Appearance
Store Status: check that your data jobs ran on time
Settings > Store Status answers one question: did the scheduled jobs that feed Nexus run on time? Open it when a number looks stale or missing. It also lists errors that affect your store.
Problem and intended user
The ecommerce manager (the person who runs the store) sees a number in Nexus that looks old or wrong. The cause may be a late data job, a failed sync or a lost connection. Without a check, the ecommerce manager cannot tell a real change in the store from data that did not arrive. Decisions can then rest on stale figures.
Current workflow
Without Store Status, a merchant compares a Nexus figure with Shopify admin reports, Meta Ads Manager, Google Ads or GA4. When the figures differ, the merchant checks each connection one by one, or asks support or an agency to look. Nothing in that routine says whether the gap comes from the source or from a late sync.
Prerequisites
- The Shopify app is installed for your store.
- A job row appears only when the matching integration is connected. See Integrations overview.
A store with no tracked jobs shows No tracked jobs or data sources yet.
How Nexus works
Nexus records the last run of each scheduled job and the last sync of each connected data source. It then compares each run with the time the job should have run by. Fixed rules produce every verdict and badge on the page. AI writes none of it. Nothing on this page needs your approval, and you change nothing here. The page is read-only.
A job row appears only when its integration is connected. Review jobs appear once for each connected review platform.
Read the verdict
A banner at the top gives the overall result, with a one-line summary under it. The summary counts the issues, or the items that are behind schedule.
| Banner | Meaning |
|---|---|
| All systems on schedule | Every tracked job is on time and no error is listed. |
| Some jobs need attention | At least one job is behind, or the page lists a warning. |
| Action needed | At least one job failed, or the page lists an error. |
Read the job sections
Jobs sit in sections, in this order:
- Web analytics
- Catalog & products
- Customer intelligence
- Advertising
- Daily intelligence
- Supplementary signals
- Connected integrations
A section with no rows does not appear. The exception is Catalog & products, which still appears when it carries the category notice below. Each row shows the job name, a status badge and a short description of how often the job runs.
Status badges
| Badge | Meaning |
|---|---|
| On track | The job ran when it should have. |
| Behind | The job has not run within its expected window. |
| Failed | The last run ended in an error. |
| Never run | The job has not run yet for your store. |
| Not enabled | The job is off for your store on purpose. This is not a fault. |
| Running… | The job is working now. It has not missed its window. |
The Customer segments (RFM) row tracks the daily update of each customer's RFM group and score in Shopify. Nexus writes them to your Shopify customers as tags. The row detail reads N customers updated after a run. The update does not run until the Customer segments app block is on your published theme. When Nexus skips it for that reason, the row shows Not enabled with the hint Add the Customer segments app block to your theme to enable.
Times on each row
- Last run shows how long ago the job ran, for example 3h ago. It reads never when the job has not run.
- Some jobs have no run record. These show Last data with (approx.). The time is when the job last produced data, estimated rather than read from a run record. Review rows read this way too while the review app is connected.
- Ran in shows how long the last run took.
- Next shows the next expected run in UTC, for example Oct 7, 04:00 UTC. It appears only for a row with a fixed daily time. The Morning brief row and the review rows show no Next.
Schedules shown on the page
Each row prints its own cadence under the job name. The table lists the main rows and quotes the text as the page prints it. A row appears only when its integration or data is connected. Nexus updates these jobs on its own. You cannot start any of them from Settings > Store Status.
| Row | Cadence text on the row | When the row appears |
|---|---|---|
| Meta ads sync and Google ads sync | Daily · 04:00 UTC | That platform is connected. |
| Triple Whale sync | Daily · 05:30 UTC | Triple Whale is connected. |
| Competitor ad tracking | Daily · 04:30 UTC | An ad platform is connected and you track competitors. The row shows Last data with (approx.). |
| Ad performance rollup | Daily · 05:00 UTC | An ad platform is connected. |
| Ad intelligence synthesis | Daily · 04:30 UTC | An ad platform is connected. |
| Product catalog sync | Daily · 03:00 UTC | Always. |
| Product scoring | After each catalog sync | Always. |
| Product relationships | Daily · 05:30 UTC (at most once per 7 days) | Your order data is connected. |
| Product stickiness | Daily · 06:00 UTC (at most once per 7 days) | Always. |
| The daily sync of your order and customer data | Daily · 02:00 UTC | Your order data is connected. |
| Customer segments (RFM) | Daily · 07:00 UTC | Your order data is connected. |
| Segment migration snapshot | Daily · 06:00 UTC | Your order data is connected. |
| Customer transition insights | Daily · 06:30 UTC | Your order data is connected. |
| NPS intelligence | Daily · 07:00 UTC | Your order data is connected. |
| Daily insights analysis | Daily · 06:00 UTC | GA4 is connected. |
| Product classification (GA4) | Daily · 06:00 UTC | GA4 is connected. |
| Morning brief | Daily · 07:00 store-local | Always. |
| A row named after each review app, such as Judge.me reviews sync | Daily | The review app is connected. |
| CSV Import reviews | Manual import | You imported reviews from a CSV file. |
Rows that read On demand run when something triggers them. Every row under Connected integrations reads Continuous.
The text (at most once per 7 days) means that Nexus checks daily and refreshes a store about once a week. Compute Relationships, Compute Stickiness and Recalculate are the on-demand controls, and they sit on their own pages.
The Competitor ad tracking, Ad performance rollup and Ad intelligence synthesis rows never show Behind. Creative Radar has no row on this page.
Exact output
The page shows the verdict banner, the job sections, the list of errors and a time stamp.
Errors affecting your store
Under Errors affecting your store, each entry shows its source, how long ago it happened and a message. Amber entries are warnings. Red entries are errors. An entry shows the latest run of a job and stays until that job runs again. The error text of a failed sync appears here, not on the job row. When nothing failed, the list reads No errors in the tracked window.
Products with no Shopify category
In Catalog & products, a notice can read N products have no Shopify category. It is information, not an error. Nexus compares those products against your whole store instead of against similar products. The notice names how many products are affected and the total that Nexus compares store-wide.
The notice appears only when Nexus decides it is worth showing, and it stays until you set categories. Select Add categories in Shopify to open your product list in Shopify Admin. In Demo Mode, or when Nexus cannot build that link, the link reads How to set a product category and opens Shopify's own instructions.
Snapshot time
The page ends with Snapshot generated, which says how long ago Nexus built this view.
What to do with it
| What you see | Decision or action | Owner |
|---|---|---|
| All systems on schedule | Trust the numbers in Nexus. No action. | Ecommerce manager |
| Some jobs need attention with a Behind badge | Wait for the next run shown under Next, when the row shows one. Check again after it. | Ecommerce manager |
| Action needed or a red error entry | Read the message. Follow Troubleshooting. If the error stays, use Contact support. | Ecommerce manager |
| A failed or Behind row in Connected integrations | Check the connection in your integrations. See Integrations overview. | Ecommerce manager |
| N products have no Shopify category | Select Add categories in Shopify and set categories in Shopify Admin. This happens outside Nexus. | Ecommerce manager |
| Never run right after install | Wait. See While your data imports. | Ecommerce manager |
An error here is a symptom, not a to-do list.
Expected value and measurement
Store Status can help you tell late data from a real change in your store. It can also help you find a failed connection sooner.
To check it, open Settings > Store Status when a number looks off. Compare the banner and the Last run time of the matching job with the page that shows the number. A Behind or Failed badge on that job points to a data cause. An On track badge points to the store itself.
Nexus has no page that counts how often jobs ran late over time, so you cannot track a trend. The effect on your decisions cannot be isolated from other changes in your store.
Limitations and exceptions
- The page shows only jobs for integrations you connected. A missing section means the integration is not connected, not that a job failed.
- Not enabled is not a fault. The job is off on purpose for your store.
- Never run and Not enabled do not change the verdict. A store whose jobs never ran can still read All systems on schedule.
- A job that shows Running… counts as on time in the verdict.
- Rows marked (approx.) show an estimated time, not a recorded run.
- The category notice is not an error and does not change the verdict. Adding a category does not promise a different comparison. A category forms a peer group only when enough other products share it.
- The notice does not appear for every store. Nexus shows it only when it judges it useful.
- If the page cannot load, it shows Could not load store status. Reload the page. If it persists, use Contact support.
- If Nexus fails to read a source of status data, a warning in the error list says that the page shows partial results.
- The Google ads sync row can read Failed, and Errors affecting your store then lists a Performance Max message. It says that Performance Max spend has not synced since a given date, and that asset-group spend is missing from Ad Performance. This can happen even when the sync ran. Select Sync Now on Performance > Ad performance to start a sync. See Ad performance.
- A review app whose connection is lost reads Failed, and the error list tells you to reconnect it in Settings > Integrations. See Review apps.
- In Demo Mode the page shows sample data for a fictional store, with a sample-data badge.