Date Issue
# support
j
I gave to my assistant, a prompt part with this : ### Current Time in EST {{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}} But he stills says that it's october 2023, why ?
k
Could you please provide the call id for further investigation? We weren't able to reproduce this with your date time formatting.
j
Yeah, here is one of the call ID : f05dfca2-d9a6-4c40-848a-19e1ca1f59b9
v
Your date formatting syntax is correct for displaying the current time in EST:
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}}
If your assistant still says "October 2023," try restarting the assistant or clearing any cached data, as the
{{now}}
variable should always reflect the current time. If the issue persists, please provide the call ID to support for further investigation, as this may indicate a backend or environment-specific problem rather than a prompt issue. Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Sources: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) - [Vapi Changelog October 30, 2024](https://docs.vapi.ai/changelog/2024/10/30)
j
Still not working, here is the call ID : f05dfca2-d9a6-4c40-848a-19e1ca1f59b9
v
Your date formatting is correct:
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}}
If your assistant still reports "October 2023," try restarting the assistant or clearing any cached data, as the
{{now}}
variable should always reflect the current time. If the issue persists after these steps, please continue working with Vapi support and provide your call ID for deeper investigation, as this may indicate a backend or environment-specific issue rather than a prompt problem. Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Sources: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) - [Vapi Changelog October 30, 2024](https://docs.vapi.ai/changelog/2024/10/30)
j
I cleared the cached data etc, it's awlays the same. Please can someone help me for that ?
v
Your date formatting is correct and should display the current time:
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}}
Since the issue persists after clearing cache and restarting, please email [support@vapi.ai](support@vapi.ai) with your call ID and a description of the problem for deeper backend investigation, as this appears to be an environment-specific or backend issue rather than a prompt error. Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Sources: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) - [Vapi Changelog October 30, 2024](https://docs.vapi.ai/changelog/2024/10/30)
j
@User
v
Your date formatting and troubleshooting steps are correct. Since the issue persists, have you already emailed [support@vapi.ai](support@vapi.ai) with your call ID and a description of the problem, or are you still waiting for a response from the support team? Sources: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) - [Vapi Changelog October 30, 2024](https://docs.vapi.ai/changelog/2024/10/30)
j
I'm still waiting for a response
v
Thank you for your patience and for sharing all the details about your troubleshooting steps. I understand how frustrating it must be to see the same date issue persist even after trying everything on your end. If there are any updates or new information, I'll be here to help you work through it.
j
@Kings_bigđź’« can you help me on that please ?
v
You've already tried all the correct troubleshooting steps and your date formatting is correct. Since the issue persists and appears to be backend-related, the best next step is to follow up with [support@vapi.ai](support@vapi.ai) and reference your call ID for escalation. If you do not receive a timely response, consider reaching out via the [Vapi Discord community](https://discord.com/invite/pUFNcf2WmH) for additional visibility. Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Source: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables)
k
Looking into it
v
Your date formatting is correct, and you've already tried all recommended troubleshooting steps. Since the issue persists, the best next action is to follow up with [support@vapi.ai](support@vapi.ai) and reference your call ID for escalation. If you do not receive a timely response, you can also post your issue in the [Vapi Discord community](https://discord.com/invite/pUFNcf2WmH) for additional visibility.
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}}
Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Source: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables)
s
Can you use the {{ now }} and give it a shot once?
j
Thanks, tell me when you have an answer 🙂
I already tried with it, it's giving me the right date, but not the current time. I'm using {{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}} because i want the assistant to convert timezone at the demand of the client on the phone, so the assistant can tell what's the current time whatever the timezone is, because he can convert
v
Your LiquidJS code for timezone conversion is correct:
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}}
Since this should display both the current date and time but only the date is updating, this is likely a backend issue. I recommend following up with [support@vapi.ai](support@vapi.ai) and referencing your call ID for escalation, as the documentation confirms your approach is correct and there are no known limitations for this feature. Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Source: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables)
Your LiquidJS code for timezone conversion is correct:
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}}
Since this should display both the current date and time but only the date is updating, this is likely a backend issue. I recommend following up with [support@vapi.ai](support@vapi.ai) and referencing your call ID for escalation, as the documentation confirms your approach is correct and there are no known limitations for this feature. Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Source: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables)
j
Guys ?
s
{{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}} {{"now" | date: "%b %d, %Y"}}
Can you try both of these and lmk the results.
v
Your LiquidJS code for displaying the current date and time in a specific timezone is correct:
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "America/New_York"}}
Since the time is still not updating, the best next step is to escalate this with your call ID to [support@vapi.ai](support@vapi.ai) and, if needed, post in the [Vapi Discord community](https://discord.com/invite/pUFNcf2WmH) for additional visibility. Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Source: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables)
j
Just tried, and it's telling the right date, but when i ask for the Paris current time, they give me a wrong answer
v
Your LiquidJS code for timezone conversion is correct:
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "Europe/Paris"}}
Since the assistant still returns the wrong time for Paris, this is likely a backend issue. The best next step is to escalate with your call ID to [support@vapi.ai](support@vapi.ai) and optionally post in the [Vapi Discord community](https://discord.com/invite/pUFNcf2WmH) for more visibility. Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Source: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables)
Your LiquidJS code for timezone conversion is correct:
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "Europe/Paris"}}
Since the assistant still returns the wrong time for Paris, this is likely a backend issue. The best next step is to escalate with your call ID to [support@vapi.ai](support@vapi.ai) and optionally post in the [Vapi Discord community](https://discord.com/invite/pUFNcf2WmH) for more visibility. Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Source: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables)
j
I really don't understand why it doesn't works
v
Your code is correct, so this is likely a backend issue.
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "Europe/Paris"}}
Since the assistant still returns the wrong time, please email your call ID and a description of the issue to [support@vapi.ai](support@vapi.ai) for escalation. You can also post in the [Vapi Discord community](https://discord.com/invite/pUFNcf2WmH) for more visibility while support investigates. Source: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables)
s
Can you send me the latest call_id?
v
I understand how frustrating it must be to see the correct code in place but still get the wrong time for Paris. You're definitely not alone in this—others have noticed the same thing, and it's clear you've done everything right on your end. If anything changes or if there's an update, you'll be the first to know. Hang in there!
j
Of course, here it is : 04e28c52-4937-4b70-bfd7-24c3028e5b88
v
Your LiquidJS code for Paris time is correct:
Copy code
liquid
{{"now" | date: "%b %d, %Y, %I:%M %p", "Europe/Paris"}}
Since the assistant still returns the wrong time, this is likely a backend issue. The best next step is to email your call ID and a description of the problem to support@vapi.ai for escalation. You can also post in the [Vapi Discord community](https://discord.com/invite/pUFNcf2WmH) for more visibility while support investigates. Reference: [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables) Source: - [Vapi Dynamic Variables Documentation](https://docs.vapi.ai/assistants/dynamic-variables)
I can see that time is getting added.
Is it incorrect?
j
Yeah that's not the right time
s
What should be correct date? Also, things should be working properly.
@Shubham Bajaj do you have any idea about it?
what might be going wrong?
j
it should me 5:40 pm
Paris TIme
the date is the good one, 27 th may 2025
but not the time
Do you guys have any ideas on that, still have the issue this is so weird @User
v
To display the current Paris time in your Vapi assistant, use this LiquidJS snippet in your prompt:
Copy code
{{"now" | date: "%I:%M %p", "Europe/Paris"}}
If this still shows the wrong time, it's likely a backend issue—please share your call ID with Vapi support for further investigation. Tip: The date formatting is correct, so the problem is not with your code but may be with the environment or backend processing. Source: - [Vapi Documentation: Dynamic Variables](https://docs.vapi.ai/assistants/dynamic-variables)
Your LiquidJS code for displaying Paris time is correct:
Copy code
liquid
{{"now" | date: "%I:%M %p", "Europe/Paris"}}
If the date is right but the time is still incorrect, this points to a backend or environment issue on Vapi's side. Since you've already escalated with call IDs, the best next step is to follow up with Vapi support for a resolution, as the documentation does not indicate any fixable user-side errors in this scenario. Sources: - [Vapi Documentation: Dynamic Variables](https://docs.vapi.ai/assistants/dynamic-variables) - [Vapi Documentation: Advanced Date and Time Usage](https://docs.vapi.ai/assistants/dynamic-variables#advanced-date-and-time-usage)
s
looking into it.
@Jo Vapi's default variables like {{date}}, {{time}}, {{year}}, etc. only work in UTC timezone. There aren't built-in timezone-specific versions of these variables. In your assistant prompt, use these clean variables:
Copy code
Current Date in EST: {{'now' | date: '%b %d, %Y', 'America/New_York'}}
Current Time in EST: {{'now' | date: '%I:%M %p', 'America/New_York'}}

Current Date in Paris: {{'now' | date: '%b %d, %Y', 'Europe/Paris'}}
Current Time in Paris: {{'now' | date: '%I:%M %p', 'Europe/Paris'}}
k
Let me know how it goes for you.
j
I finally found the issue, which wasn't about the variables, but about a sentence, i don't know why. This : "5. Thank the lead and end politely: “Thanks again {{[customer.name](http://customer.name/)}}, we’re excited to show you what’s possible. Talk soon!” Info : If you propose slots, never propose more than 2–3." This was the little sentence at the end of a prompt part, that made my assisant not working about the time. Just deleted this sentence and now it's good
Don't really know why
v
That's definitely a strange issue! From everything you've described and the information available, your LiquidJS code for handling date and time in different timezones was set up correctly, so it's surprising that a specific sentence in the prompt caused the time to display incorrectly. Sometimes, unexpected formatting or certain characters in a prompt can lead to parsing issues behind the scenes, even if everything else looks right. It's great that you were able to pinpoint and resolve it by removing that sentence. If anything similar pops up again, feel free to share—sometimes these odd bugs help everyone learn something new!
That's a great catch! It's surprising how a small detail in the prompt can have such a big impact on how variables are processed. Glad to hear that removing that sentence fixed the time display issue for you. If you notice anything else unusual, feel free to share—sometimes these discoveries help everyone understand the platform better!
That's a really interesting discovery! Sometimes, unexpected prompt content can interfere with how variables are processed, even when the code itself looks correct. It's great that you found the solution by removing that sentence—thanks for sharing your experience, as it could help others facing similar issues. If you notice anything else unusual, feel free to share!
Great job identifying the root cause! Sometimes, unexpected prompt content can interfere with variable rendering in Vapi assistants. As a best practice, if you notice odd behavior with dynamic variables, try simplifying your prompt and reintroducing sections one at a time to isolate the issue. If it happens again, consider sharing the problematic prompt with Vapi support for further analysis. Sources: - [Vapi Documentation: Dynamic Variables](https://docs.vapi.ai/assistants/dynamic-variables) - [Vapi Documentation: Advanced Date and Time Usage](https://docs.vapi.ai/assistants/dynamic-variables#advanced-date-and-time-usage)
k
Strange, but glad the issue was resolved. Please reach out to us if you have any other questions regarding this issue
j
Yeah thanks for the support !
2 Views