https://retellai.com/?utm_source=discord&utm_medium=seo logo
why does tomorrows date not be said correctly usin...
# ❓・ai-evy-support
v
@AI Evy why does tomorrows date not be said correctly using the system variablke
a
Thanks for tagging me @Vyyy. I'll look through relevant sources and get back to you shortly.
### Answer The system variable
{{current_time}}
provides the current date and time, not tomorrow's date [(1) ]() . If you need the agent to reference tomorrow's date, you'll need to handle this in your prompt by instructing the agent to calculate it based on the current time . The available system variables related to time are : -
{{current_time}}
- Current time in America/Los_Angeles -
{{current_time_[timezone]}}
- Current time in specified timezone -
{{current_hour}}
- Current hour as a fraction in America/Los_Angeles -
{{current_hour_[timezone]}}
- Current hour as a fraction in specified timezone -
{{current_calendar}}
- 14-day calendar in America/Los_Angeles -
{{current_calendar_[timezone]}}
- 14-day calendar in specified timezone For handling relative dates like "tomorrow," you can use the
{{current_calendar}}
variable which provides a 14-day calendar . Then in your prompt, instruct the agent to interpret relative terms based on this calendar. If you're experiencing issues where the date appears incorrect, try clearing your browser cache or testing in a different browser, as browser-specific glitches have been reported [(2) ]() .
​ To learn more, see the sources I considered: [[1] Dynamic Variables](https://docs.retellai.com/build/dynamic-variables) [[2] when using {{current_time}}, it says todays date is Jan 29th](https://discord.com/channels/1186424376300679209/1341124870922174587) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
v
@AI Evy does it cache somewhere? iit gives me a wrong date everytime
a
Thanks for the follow-up, @Vyyy. I'll get back to you soon.
​ To learn more, see the sources I considered: [[1] Dynamic Variables](https://docs.retellai.com/build/dynamic-variables) ​
### Answer Based on the available sources, I don't have specific information about caching mechanisms for dynamic variables that would cause consistently incorrect dates [(1) ]() . However, here are some troubleshooting steps you can try: 1. **Verify the timezone**: The default
{{current_time}}
uses
America/Los_Angeles
timezone . If you need a different timezone, use
{{current_time_[timezone]}}
format, for example
{{current_time_Australia/Sydney}}
. 2. **Check your prompt carefully**: Ensure you're using the correct variable syntax with double curly braces exactly as
{{current_time}}
or
{{current_calendar}}
. 3. **Test with the calendar variable**: Try using
{{current_calendar}}
which provides a 14-day calendar view . This might give you more context about whether the date issue is with interpretation or the actual value. 4. **Review your agent configuration**: Check if there are any agent-level default dynamic variables set that might be overriding the system variables . If the issue persists across multiple calls and you're consistently getting the wrong date, I'd recommend: - Testing with a simple agent that just speaks the
{{current_time}}
value to isolate the issue - Checking the call logs to see what value is actually being passed Could you share what specific date you're seeing versus what you expect? That might help narrow down whether it's a timezone issue or something else.
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.