Dust Community Icon
Join the Community
Help

Fixing Agent Timestamp Issues for Accurate Data Retrieval

Avatar of Marty ChangMarty Chang
·
·

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?

2 comments

  • Avatar of David Ebbo
    David Ebbo
    ·
    ·

    That's quite odd. Do you see this consistently? What model are you using, and what happens if you try a different one?

  • Avatar of Marty Chang
    Marty Chang
    ·
    ·

    Good question, David. 🤔 It's currently using Claude 3.5 Sonnet and when I see this problem again I will try a different model. The workaround I ended up implementing was to change the instructions and the dataset to take relative values, then use JavaScript in a code block to get the exact dates.