weronika
04/23/2026, 1:28 PMAI Evy
04/23/2026, 1:28 PMAI Evy
04/23/2026, 1:28 PM{{current_time}} variable displaying incorrect dates. [(1) ]() [(2) ]() [(3) ]() Some users have experienced similar issues where the agent states the wrong date or time. [(1) ]() [(2) ]()
Here are some troubleshooting steps that have worked for others:
1. Try refreshing or restarting your browser - One user found that switching from Chrome to Safari resolved the issue, and restarting Chrome also helped. [(3) ]()
2. Check for test data variables - In one case, deleting test data variables in the agent configuration resolved the date issue.
3. Verify your dynamic variable syntax - Ensure you're using the correct format: {{current_time}} for America/Los_Angeles timezone, or {{current_time_[timezone]}} for a specific timezone (e.g., {{current_time_America/New_York}}) . [(4) ]()
4. Test in both the LLM test interface and actual calls - Sometimes the issue appears in one but not the other. [(1) ]()
If the problem persists after trying these steps, you may want to reach out to the Retell team directly, as there have been instances where engineering intervention was required to resolve date/time variable issues. [(2) ]()AI Evy
04/23/2026, 1:28 PMAI Evy
04/23/2026, 1:28 PMweronika
04/23/2026, 1:52 PMAI Evy
04/23/2026, 1:52 PMAI Evy
04/23/2026, 1:52 PM{{current_time}} variable "hasn't populated," this indicates the variable isn't being evaluated properly. Here's what you should check: [(1) ]()
1. Verify your variable syntax
The correct format is {{current_time}} for America/Los_Angeles timezone, or {{current_time_[timezone]}} for a specific timezone (like {{current_time_Australia/Sydney}}) .
2. Check where you're using the variable
Dynamic variables work in specific locations:
- Prompts (agent instructions)
- Begin message
- Tool configurations (custom function URLs, tool descriptions, property descriptions)
- Call handling (voicemail prompts, transfer phone numbers, warm transfer instructions)
- Webhook URLs
3. Ensure proper spacing
The spaces around the variable name are trimmed when evaluating, but make sure there are no typos or extra characters inside the curly braces.
4. Test the variable exists
You can use an equation condition to check if the variable is being set: {{current_time}} exists. This returns true if the variable is defined.
5. Check for agent-level default variables
If you've set default values at the agent level, these should serve as fallbacks. Make sure you haven't accidentally overridden {{current_time}} with a custom variable of the same name. [(1) ]() [(2) ]()
If the issue persists after verifying these points, the problem may require direct support from the Retell team, as there have been known issues with the {{current_time}} variable displaying incorrect dates.AI Evy
04/23/2026, 1:52 PMAI Evy
04/23/2026, 1:52 PMweronika
04/23/2026, 1:53 PMAI Evy
04/23/2026, 1:53 PMAI Evy
04/23/2026, 1:53 PM{{current_time}} exists in transition conditions within your Conversation Flow agent. [(1) ]()
Here's where to set this up:
1. Open your Conversation Flow in the dashboard
2. Click on a node where you want to test the variable
3. Click the "+" button to add a transition condition
4. Choose "equation" transition condition (not "prompt")
5. **Enter the equation**: {{current_time}} exists
This equation condition checks whether the {{current_time}} dynamic variable is defined and has a value. [(2) ]() [(1) ]()
Example equation conditions you can use: [(1) ]()
- {{current_time}} exists - Returns true if the variable is defined
- {{current_time}} does not exist - Returns true if the variable is undefined
Note that equation conditions are evaluated from top to bottom, and the agent will follow the first condition that evaluates to true.
If you're still experiencing issues with the variable not populating, you might also try using a Logic Split Node after your Begin node that transitions based on whether {{current_time}} exists. [(3) ]() [(4) ]()AI Evy
04/23/2026, 1:53 PMAI Evy
04/23/2026, 1:53 PM