Holiday Notice – Support Unavailable on April 18 and April 21

We just wanted to let you know that our support team will be offline on Friday, April 18th (Good Friday) and Monday, April 21st (Easter Monday) due to the holidays.
We'll be back on Tuesday, ready to assist you!

In the meantime, if you need any help, feel free to:

Amelia YouTube Channel

wpDataTables YouTube Channel

Thank you for your understanding, and we wish you a wonderful holiday weekend!

Okay
  Public Ticket #2198741
Google appointment doesn't take Daylight Saving Time changes into account
Closed

Comments

  •  4
    Remko started the conversation
    October 29, 2019 at 9:51am

    I had a client book an appointment last week: 11:30 - 13:00.
    The mail she and I received both confirmed the 11:30 appointment time.
    I also had this appointment added to my Google Calendar:  10:30 - 12:00!!

    This has never gone wrong before with other appointments: the time zone is set correctly.

    I think I know the cause for this issue: last weekend (in between the scheduling of the appointment and the appointment itself) the clock was rewinded 1 hour.

    Can you please check for any errors in this?

    Best regards, Remko

  • [deleted] replied
    October 29, 2019 at 10:38am

    Hello Remko, 

    We haven't had any troubles with the appointments and the time change so far on our testing website and no one made any complaints. But I will forward this to our development team so they can test it out. Sorry for any inconvenience this have caused. I am not sure how this time could be sent to Google Calendar if in Amelia the times are set correctly. We also have this time change and we worked on implementing it in Amelia, so there will be no issues with the time when the clock goes back.

    Could you please just tell me does everything work well now? Are the times of the appointments correct now in Amelia and in Google Calendar as well?

    Thanks!

  •  4
    Remko replied
    October 29, 2019 at 6:47pm

    Hi Marija,

    I think I found the cause of this issue: I had set my timezone to a fexed (!) GMT+2.
    Instead I should have chosen for Amsterdam, for which the time automatically adjusts itself.

    So: all is well now!!

    Thanks again!

  • [deleted] replied
    October 30, 2019 at 10:31am

    Hello Remko, 

    Great, glad to hear that !smile.png 

    Thanks for letting us know!

    If you have any further questions or concerns feel free to open a new ticket and we will gladly help,