### Answer You can't disable the

{{current_time}}

system variable, but you can work around it by using timezone-specific variants or custom dynamic variables. [(1) ]() For your +10:30 timezone (likely Australia/Adelaide) , use the timezone-specific syntax:

{{current_time_Australia/Adelaide}}

This will give you the current time in your desired timezone instead of the default America/Los_Angeles (PST) . Alternatively, you can create a custom dynamic variable that returns the current time in your timezone when the call initiates. [(2) ]() This approach gives you full control over the time format and timezone handling in your backend code. If you're using the inbound webhook, you can pass your custom time variable through the

retell_llm_dynamic_variables

field. [(1) ]() [(3) ]()

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

​ To learn more, see the sources I considered: [[1] Dynamic Variables](https://docs.retellai.com/build/dynamic-variables) [[2] Discord message from @nocodecreative.io on 2024-12-15](https://discord.com/channels/1186424376300679209/1186462578310910112/1317840635717222432) [[3] Set current_time timezone so we can provide the time in areas other than PT](https://discord.com/channels/1186424376300679209/1342615209126395995) ​

@AI Evy currentTime: 'Thursday, 2026-04-02T23:23:34+10:30', is set but the agent said it is 11:50 which is the time in melbourne https://cdn.discordapp.com/attachments/1489247730583867564/1489248532228739142/image.png?ex=69cfba46&is=69ce68c6&hm=86ce96c396f8da42e4279b5ae6275ba2c0745f2c973027495fc79ad311f71ca8&

### Answer The issue is that the system variable

{{current_time}}

defaults to America/Los_Angeles timezone and is likely overriding your custom

currentTime

variable in the prompt. [(1) ]() To fix this, you need to update your prompt to explicitly reference your custom variable instead of the system one. Make sure your prompt uses

{{currentTime}}

(your custom variable) rather than

{{current_time}}

(the system variable) . Additionally, consider simplifying the format. The LLM may struggle to parse the ISO format you're using. Try passing a more human-readable format in your custom variable: [(2) ]()

currentTime: 'Thursday, April 02, 2026 at 11:23:34 PM ACDT'

In your prompt, add explicit instructions like: [(1) ]()

The current time is {{currentTime}}. Use this time for all time-related queries.

If you're still seeing the system variable being used, check that: 1. You're passing

currentTime

in the

retell_llm_dynamic_variables

field when creating the call 2. Your prompt doesn't reference

{{current_time}}

anywhere (which would pull the PST default) 3. The variable name matches exactly between your API call and prompt (case-sensitive)

​ To learn more, see the sources I considered: [[1] Dynamic Variables](https://docs.retellai.com/build/dynamic-variables) [[2] Discord message from @nocodecreative.io on 2024-12-15](https://discord.com/channels/1186424376300679209/1186462578310910112/1317840635717222432) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer If you're not using

{{current_time}}

anywhere in your prompt and the agent is still using a different timezone, the system variables are likely being injected automatically by Retell. [(1) ]() According to the documentation, Retell automatically provides system variables including

{{current_time}}

which defaults to America/Los_Angeles timezone - no configuration required. These system variables are available to the LLM even if you don't explicitly reference them in your prompt. To ensure your custom

currentTime

variable takes precedence, try these approaches: 1. Be more explicit in your prompt instructions :

IMPORTANT: The current time is {{currentTime}}. Always use this exact time for any time-related questions. Do not use any other time source.

2. Use the timezone-specific system variable instead of a custom one :

{{current_time_Australia/Adelaide}}

This would give you: "Thursday, March 28, 2024 at 11:46:04 PM ACDT" 3. **Override at the call level**: When creating the call, you can use

retell_llm_dynamic_variables

to pass your custom time variable [(1) ]() [(2) ]() , and potentially use

agent_override

to modify the prompt to emphasize your custom variable. [(2) ]() The issue is that system variables are always available to the LLM, [(1) ]() so even though you're not explicitly using

{{current_time}}

, the LLM may be accessing it. Your best bet is either using the timezone-specific system variable syntax or adding very explicit instructions in your prompt to only use your custom variable.

​ To learn more, see the sources I considered: [[1] Dynamic Variables](https://docs.retellai.com/build/dynamic-variables) [[2] Outbound Calls (Make Calls)](https://docs.retellai.com/deploy/outbound-call) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.