Explore recipe: Creating a last refresh timestamp

Return to top

14 Comments

  • CJ

    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. 

    0
  • 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.

    0
  • 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.

    0
  • 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. 

    0
  • 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! 

    0
  • CX Automations

    Hey all,

    I am having the same issues. This recipe isn't working for me and is showing a timestamp from 2019. I'd love some help or a resolution.

    Thanks,

    Sam

    0
  • Erin O'Callaghan
    Zendesk Documentation Team

    Hi CX Automations! If you're seeing a timestamp from 2019, a quick thing to check is whether the Top/bottom attribute is set correctly. You'll want to make sure the top field is set to 0 and the bottom field is set to 1. (If those two fields are switched, you'll see the oldest timestamp instead of the newest.)

    0
  • CJ

    All of the images were removed from this article, makes it rather tricky to tell what it is instructing.

    0
  • Erin O'Callaghan
    Zendesk Documentation Team

    Hi CJ, I've restored all the images in the article—sorry for the confusion!

    0
  • Monica

    The article image has MED for the metric, but the instructions have you only allow MIN. Which is the correct setting?

    0
  • Erin O'Callaghan
    Zendesk Documentation Team

    Hi Monica, the correct setting should be MIN. I've updated the screenshot so that it matches the instructions!

    0
  • Dave Symonds

    Why don't you just expose the value for use so it can be used so there is not need to write an convoluted process that actually returns an inaccurate value?

    0
  • Dave Symonds

    Question:  Whats the value of the Last ticket updated Mins represent.  I thought it would change as time progressed as it calculates against now?

    0
  • CJ

    Dave Symonds It just lets you know how out-of-date the dashboard is, if you have a plan where it updates once an hour, it's not on the hour, so it can be hard when looking at a Dashboard to tell when it last pulled in fresh data. 

    0

Please sign in to leave a comment.

Powered by Zendesk