Agent does not know year even when variable is set

Support Help
1

We have this in the global prompt and the agent is not knowing what the current date is. See below

The current date and time is {{current_time_{{agent_timezone}}}}

image
image383Ă—796 47.4 KB

2

Hey @skhandor can you share your agent id

3

agent_7f5c281b6ec8437d372525f4a7

4

@skhandor checking with the team.

5

Thanks, this is what we have for the timezone

image
image477Ă—168 8.44 KB

6

Hello @skhandor

The first screenshot is from the testing playground inside the agent. You didn’t send any variables to the call.

But it should work fine in normal calls when you send the variable. I just tested your agent by adding a default value to the agent_timezone, and it worked fine

image
image634Ă—388 21.7 KB

image
image726Ă—468 31.2 KB

7

Please see this call from production today. It thought June 25th was Tuesday:

call id: call_d5f1efd0e80e673c3c0f2c9c61a

image
image580Ă—368 30.9 KB

8

Hey @skhandor The caller said the appointment was on Thursday, June 25. The agent restated it as “Tuesday, June twenty-fifth.” June 25, 2026, is indeed a Thursday — the model dropped the caller’s weekday and reused “Tuesday” from today’s anchor. This is a known limitation: frontier LLMs don’t reliably compute the day of the week from a date string for any day other than the one already rendered for them.

Recommended fix: add a guardrail to the prompt such as:

"Never state a weekday for any date other than today’s date as given in {{current_time_{{agent_timezone}}}}. When repeating a date the caller provided, restate the month and day only — do not name the weekday unless the caller named it."

9

{{current_time_[timezone]}} should look like {{current_time_Australia/Sydney}} not {{current_time_{{agent_timezone}}}}