Can you trust the numbers in Hex?

What does Hex keep track of?

• Hex keeps a record of each scheduled run of a report for about three months, so recent runs can be looked back on.

  In Hex's own words: Past scheduled runs (and API-triggered runs) can be accessed for up to 90 days after they were executed. Scheduled runs, read 2026-11-12.

• Hex keeps a saved version of a project every time it is published, so an earlier version of a report can be found again.

  In Hex's own words: A new version will also be created each time the project is published. History and versions, read 2026-11-12.

What can make Hex's numbers look wrong?

1. A Hex report can show figures up to an hour old by default, because, as Hex's help pages say, it reuses a recent query's stored results instead of asking the database again.

   In Hex's own words: By default, results from the cache will be used if the same query has been run within the last 60 minutes. SQL query caching, read 2026-11-12.

2. Running a Hex app does not always mean every number on it is fresh, since Hex's help pages say the results can still carry the age of the oldest data it reused.

   In Hex's own words: In these cases you may have just run the app, but the age of results will continue to reflect the oldest data. Running apps, read 2026-11-12.

3. A scheduled run can finish without changing what others see in a published Hex app, because, as Hex's help pages explain, runs set up by someone with Can explore permission never update the published results.

   In Hex's own words: In contrast, scheduled runs created by users with Can explore permissions will never update the published results. Scheduled runs, read 2026-11-12.

4. If a scheduled run is canceled, the published Hex app keeps showing its older numbers, as Hex's help pages say.

   In Hex's own words: Canceled runs will be marked as failed in the Run log, and will not update the published results of the app. Scheduled runs, read 2026-11-12.

How do I check Hex's numbers myself?

1. To see current figures in a Hex app, use its Refresh button, which runs it again without reusing stored results.

   In Hex's own words: An app can be rerun without cached results via the Refresh button. SQL query caching, read 2026-11-12.

2. Look at the result age Hex shows on an app to see roughly when the numbers on screen were produced.

   In Hex's own words: Generally, you can think of this as the timestamp of the run that produced the outputs you're viewing. Running apps, read 2026-11-12.

How does Hex work with Feder?

Connect Hex to Feder and it joins your Visits apps. Feder only reads. It never changes anything in Hex.

When you connect Hex, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.

Other apps that feed Visits

• Google Adsad clicks
• Google Analyticspage views and sessions
• Everflowunique clicks
• Pendopage views

Questions owners ask about Hex

• Why don't the daily visit numbers in Hex match my other tools?Hex charts show times in the workspace time zone, so a day's visits can be split at a different midnight than in the tool you compare with.
• Why do my teammates see a different visits number in Hex?Where each person's results are kept to themselves, two people can be looking at results from different runs taken at different times.
• Why did my visits number in Hex stop updating?Where a data connection signs in to the warehouse as each person, that sign-in lapses after a while, and queries can stop until it is renewed.

See every connection.

Where do these answers come from?

Everything this page says about Hex comes from Hex's own pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.