Hello, I have a problem with timezone. I am in Europe/Prague time zone. I have confirmed that in assistant prompt and in Tool functions. Regardless I am still getting ISO formatted date's like this: 2024-10-04T14:00:00.000Z. This one was supposed to be 4pm, but vapi said no and made it 2pm. Why is that happening and how do I fix that? I am using the same timezone in Vapi, Make and airtable.

@Radim Kopp Hello! It seems like there might be a misunderstanding with time zones and ISO formatted dates. The date you're seeing,

2024-10-04T14:00:00.000Z

, is actually in UTC (Coordinated Universal Time), as indicated by the 'Z' at the end. This is a common format for APIs and systems to exchange date and time information because it avoids ambiguity across different time zones. To see this time in your local time zone (Europe/Prague), you would need to convert it from UTC to your local time. Europe/Prague is typically in Central European Time (CET) or Central European Summer Time (CEST), depending on daylight saving time. CET is UTC+1, and CEST is UTC+2. If the time you're seeing is 2pm UTC, then for Europe/Prague it would be: - 3pm during standard time (CET, UTC+1) - 4pm during daylight saving time (CEST, UTC+2) To fix this issue, you should ensure that the time conversion is handled correctly in your application. If you're using VAPI, Make, and Airtable, you'll need to check the settings in each of these services to ensure they are set to handle the Europe/Prague time zone correctly. If you need further assistance with this, please let me know more details about where the conversion is going wrong, and I'll be happy to help you troubleshoot the issue.

I just said that I am using the exact same timezone everywhere, but I am still getting UTC

@Radim Kopp Hello! It seems like there might be a misunderstanding with time zones and ISO formatted dates. The date you're seeing,

2024-10-04T14:00:00.000Z

, is actually in UTC (Coordinated Universal Time), as indicated by the 'Z' at the end. This is a common format for APIs and systems to exchange date and time information because it avoids ambiguity. Since you are in the Europe/Prague time zone, which is typically UTC+2 during Central European Summer Time (CEST) or UTC+1 during Central European Time (CET), you would need to add the appropriate offset to the UTC time to get your local time. For example, if it's during CEST, 2 PM UTC would be 4 PM in Prague. To fix this, you should ensure that when you display the time, you apply the correct time zone offset for your region. If you're using a programming language or a system that supports time zone conversions, you should be able to convert the UTC time to your local time zone automatically. If you're still experiencing issues with time zone conversions in your setup with VAPI, Make, and Airtable, please make sure that all systems are configured to use the correct time zone settings and that any conversion is done considering daylight saving time changes if applicable. If you need further assistance with a specific part of your setup, please provide more details, and I'll be happy to help you troubleshoot the issue.

So you're saying that I will only get time in UTC from API and I will need to convert it everytime into CET?

@Radim Kopp Yes, that's correct. APIs often provide dates and times in UTC to maintain consistency across different systems and time zones. When you receive a time in UTC, you will need to convert it to your local time zone, in this case, CET/CEST for Europe/Prague. Most programming languages and systems have built-in functions or libraries to handle time zone conversions. You can use these to convert the UTC time to your local time zone before displaying it to users or using it in your application. If you're working with a specific programming language or system and need assistance with the conversion, please let me know, and I can provide more detailed guidance on how to perform this conversion.