Has anyone else resolved an issue where the agent thinks it's in 2024, not 2025? I'd appreciate guidance on how to reliably nix this problem. 🙏
The problem: My agent is configured with an instruction to gather historical data from the last 30 days. Then, it runs a Dust app to pull the relevant info from an API. The Dust app uses a dataset that includes start and end properties, described as follows.
start: The UNIX timestamp indicating the start of the time interval.
end: The UNIX timestamp indicating the end of the time interval.
The app ran, but the agent put in timestamps for 27 March 2024 and 25 Apr 2024 instead of 2025! 😱 Is there a way to ensure the agent is always operating with awareness of the real, current time?