Explore recipe: Creating a last refresh timestamp

Return to top


  • CJ Johnson

    It looks like this unfortunately doesn't work anymore. It says this queries too many rows, and snips the data, so the timestamp is shows is way off (like, it showed me a timestamp with the year 2013). 

    Edit: The easy fix: For most folks, add in a "Ticket Updated - Date" filter set for "Today". You might get weird results for midnight runs, or if your data updates daily instead of hourly, but otherwise should avoid data overload and getting a wildly wrong date. 

  • Kate L

    Hi CJ,

    Apologies for the delay here. I have created a ticket on your behalf so we can look into your query further.

  • Brandon Niblock

    It does appear to no longer work. Even with the steps CJ added its still off.  Right now the data set is 34 minutes last update, this formula is showing 86 minutes.

  • Darenne
    Zendesk Customer Care

    Hi Brandon, 

    Apologies for the delayed response. In order for us to properly investigate this, I've created a ticket on your behalf to look into this further. 

  • Erin O'Callaghan
    Zendesk Documentation Team

    Hi all, I just wanted to post a quick note to clarify how this recipe works, in light of a few of the comments above:

    • The built-in dataset sync timestamp in the upper left of the query builder measures the last time Explore's behind-the-scenes process ran to update data, regardless of whether there was actually new data to be updated.
    • The timestamp created by this recipe, on the other hand, measures the last time a ticket was updated as long as the update happened before the last dataset sync. (Otherwise Explore wouldn't know about that ticket update because the sync hasn't run yet.)

    So while this recipe isn't an exact replacement for the dataset sync timestamp, it's still a useful way for dashboard viewers to know approximately how current the info on a dashboard is. Hope that helps! 


Please sign in to leave a comment.

Powered by Zendesk