Why did my visits number in Hex stop updating?
The Hex help pages give 4 common reasons. The first to rule out: 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.
What causes it?
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.
In the Hex help:
OAuth tokens expire after a set period (based on how the warehouse OAuth client is configured).
OAuth data connections | Learn | Hex Technologies, read 2026-11-12.A scheduled run on such a connection can fail until the person who owns the schedule signs in again, so the numbers can stay where they were.
In the Hex help:
Scheduled runs may fail until the owner refreshes credentials.
OAuth data connections | Learn | Hex Technologies, read 2026-11-12.Apps refresh on their own by default, but someone who edits the project can turn that off, which leaves older results on show.
In the Hex help:
A user with Can edit or higher project permissions may have turned off auto-refresh.
Running apps | Learn | Hex Technologies, read 2026-11-12.If the project behind the visits report was archived, its scheduled runs no longer happen.
In the Hex help:
Scheduled runs are disabled on archived projects.
Scheduled runs | Learn | Hex Technologies, read 2026-11-12.
How do I check it myself?
Ask Hex to tell you when a scheduled run finishes or fails, so a run that stopped is noticed the same day.
In the Hex help:
Get notified when a scheduled run completes (with optional file attachments), or be notified if the scheduled run errors.
App notifications | Learn | Hex Technologies, read 2026-11-12.If the connection signs in as you, sign in to the warehouse again and see whether the numbers move.
In the Hex help:
Sign in to the warehouse again if the token expires.
OAuth data connections | Learn | Hex Technologies, read 2026-11-12.Refresh the app and compare, to tell results that are simply older from a run that did not happen.
In the Hex help:
Consider refreshing the app for newer results.
Running apps | Learn | Hex Technologies, read 2026-11-12.
How does Hex work with Feder?
- Connect Hex to Feder and it joins your Visits apps.
- 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.
Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.
See whether you can trust the numbers in Hex, one of your Visits apps. Feder only reads. It never changes anything in Hex.
What else goes wrong with these numbers?
- Why don't the daily visit numbers in Hex match my other tools?Hex
- Why do my teammates see a different visits number in Hex?Hex
- Why did Google Analytics stop collecting data?Google Analytics
- Why aren't my key events showing in Google Analytics?Google Analytics
- Why does Google Analytics show (not set)?Google Analytics
See every question.
Where do these answers come from?
Every cause and check on this page comes from the Hex help 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.