VAPI•5mo ago

Vapi HighLevel integration is stuck on 2024

Vapi HighLevel (Check-Calendar) integration is stuck on 2024

e446b652-43e5-4740-8882-2e7ada4a2c39 / bb491a3b-5660-4037-8c37-06898e34f77e

In agent prompt I state:
TimeNow is : {{"now" | date: "%A, %B %d, %Y, %I:%M %p", "Europe/Bucharest"}}

In function description I state:
TimeNow is : {{"now" | date: "%A, %B %d, %Y, %I:%M %p", "Europe/Bucharest"}}

It still uses 2024 as reference year

improved-purple•7/25/25, 4:09 PM

Reach out to the team for enquires and assistance•

discord:/#@%64%69%73%63%6F%72%64%61%70%70%2E%63%6f%6d/%69%6e%76%69%74%65/%4E%38%37%61%4E%78%56%33%37%48
@Sipy

VapiAPP•7/30/25, 1:28 AM

Hi Sipy,

To address the issue with the date being stuck in 2024, make sure that your assistant is correctly pointing to the live updated date and time using the format you've already included in your prompt and function description. Here's a checklist to help ensure the date updates correctly:

Verify API Configuration: Ensure your Vapi AI configuration is up-to-date and consider reapplying the code snippet to refresh the settings.
Time Zone: Double-check the specified time zone ("Europe/Bucharest") to ensure it is correctly reflected in your environment settings.
Dynamic Variables: Confirm that your assistant's environment supports the dynamic variable for date-time you are implementing: {{"now" | date: "%A, %B %d, %Y, %I:%M %p", "Europe/Bucharest"}}{{"now" | date: "%A, %B %d, %Y, %I:%M %p", "Europe/Bucharest"}}.

It might also help to test this setup in a sandbox environment to see if the issue replicates there or if it's specific to your current setup.

For further details, refer to the documentation on dynamic variables usage.

Variables | Vapi

Personalize assistant messages with dynamic and default variables

Vapi HighLevel integration is stuck on 2024

Similar Threads

Similar Threads

Similar Threads