Troubleshoot Reporting Delays in DataNow

Description: This guide explains why DataNow reports may show outdated figures or stop updating during a live event, how to tell whether it is a temporary delay or a real issue, and what to do while waiting for data to catch up.

Important: DataNow showing stale data does not affect your ability to process orders or take payments. Sales continue normally regardless of what DataNow is displaying.

How DataNow Gets Its Data

DataNow pulls data from a replica of the primary database — not the primary database itself. This is by design: separating reporting from the live transaction database protects order processing performance. It also means there is always a small delay between when an order is placed and when it appears in DataNow.

• Normal refresh cadence: 5 to 15 minutes. A new order placed at the POS will typically appear in DataNow within this window under normal conditions.
• During high load periods: On busy event days with high order volume, the delay may extend beyond 15 minutes as the replica works to catch up with a higher volume of incoming data.
• Replica lag: If the replica database falls significantly behind — due to a database optimization job, an infrastructure spike, or sustained high load — DataNow may stop showing new data entirely until the replica catches up. This is the most common cause of DataNow appearing to freeze during a live event.

Quick Diagnosis

Use this table to identify what you are most likely experiencing:

DataNow Stopped Updating Mid-Event

This is the scenario that comes up most frequently during live events — DataNow was showing data earlier in the day and then stopped refreshing. Here is what is likely happening and what to do.

What is happening

DataNow reads from a replica database. When the replica falls behind the primary — either due to high query load across the ecosystem, or a background database job that takes longer than expected — new records stop appearing in DataNow until the replica catches up.

Important: This does not affect order processing. Transactions are being captured and payment is being taken normally. Only the reporting view is delayed.

What to do

1. Do not panic. Sales are still being processed and captured. DataNow will catch up.
2. Wait 5–10 minutes and refresh the report. In most cases replica lag resolves on its own within minutes.
3. Check Device Monitoring. If devices are showing as synced in Device Monitoring, the orders exist in the system and will appear in reports once the replica catches up.
4. Check for unsynced orders. In Sales Hub, review the Unsynced Orders tile to confirm whether devices have outstanding offline orders. These are a separate issue from replica lag and need to be synced separately.
5. If DataNow has not updated for more than 30 minutes during an active event, contact support. Provide the venue name, the time data last appeared to update, and the approximate number of orders you believe are missing.

What support will check

When escalated, the infrastructure team can monitor replica lag in real time and confirm whether the issue is resolving. In most cases the replica catches up without intervention. If the lag is severe, a secondary replica can be brought online as a fallback.

Data Appears Stale After Refreshing

If you are manually refreshing the DataNow report and figures are not changing, check the following before escalating:

• Browser cache: Try a hard refresh (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac) or open DataNow in a private / incognito browser window.
• Calendar Date filter: Confirm the date filter is set correctly. A filter locked to a specific past date will not update even if new orders are being placed today.
• Time zone: If the viewer time zone does not match the venue's time zone, reports may appear to show data from a different window than expected.
• Report tab: The This Month tab includes current month data plus the last 7 days of the prior month. The Last 12 Months tab uses a cached historical data source that updates less frequently than the This Month or Today tabs.

Login Issues — "Something Went Wrong" or "Authenticating"

If a user can log into Canopy successfully but DataNow shows an "Authenticating" message followed by a red "Something went wrong" error, the most common cause is an outdated DataNow URL.

DataNow is accessed via a venue-specific URL. Over time, some older URLs can fall out of date as the platform is updated. If a user is bookmarking or accessing an old URL, it may no longer work correctly even though their account permissions are valid.

What to try:

• Confirm the user is accessing the correct, current DataNow URL for their venue. If unsure, navigate to the venue's Canopy instance and access DataNow from there.
• Try a different browser or clear browser cache and cookies.
• Try opening DataNow in a private / incognito browser window.
• If the issue persists across browsers and devices, contact venuesupport@shift4.com with the URL the user is attempting to access and the specific error message displayed.

Note: A red error popup is typically a URL or session issue. A full-page error with a blue logout button indicates a different type of authentication problem and should be escalated to support directly.

Frequently Asked Questions

Does DataNow going stale mean our sales are being lost?

No. DataNow is a reporting view that reads from a replica database. Order processing runs independently and is not affected by replica lag. Sales are captured and payment is taken as normal — DataNow simply hasn't displayed the new records yet.

How long should I wait before escalating?

If DataNow has not shown any new data for more than 30 minutes during an active event, that is a reasonable threshold to contact support. Brief delays of 5–20 minutes during busy event periods are normal and will self-resolve.

DataNow was working earlier today. Why did it stop mid-event?

The most common cause during a busy event day is replica database lag — the reporting database falls behind when query volume is very high. This is typically self-resolving within minutes. Overnight database optimization jobs running later than scheduled are another known cause. These do not affect sales processing.

Can I tell if DataNow is behind or if orders are genuinely missing?

Check Device Monitoring in DataNow. If devices are showing as synced with no outstanding offline orders, the orders exist in the system and will appear in reports once DataNow catches up. If devices are showing unsynced orders, those need to be synced first before they will appear in any report.

Why does DataNow not update in real time?

DataNow reads from a replica database rather than the live transaction database. This architecture is intentional — it protects the performance and reliability of order processing by keeping reporting traffic separate. The 5 to 15 minute refresh cadence is a result of this design and is standard behavior.

A user can log into Canopy but gets an error in DataNow. Is it a permissions issue?

Usually not. The most common cause is an outdated DataNow URL. Confirm the user is accessing the correct current URL for their venue. If the URL is correct and the issue persists across browsers, contact venuesupport@shift4.com with the URL and error message.

When to Contact Support

Contact venuesupport@shift4.com if:

• DataNow has shown no new data for more than 30 minutes during an active event and you have already waited and refreshed.
• DataNow is completely unresponsive or timing out rather than showing stale data.
• A login error persists across multiple browsers and devices after confirming the URL is correct.
• You have confirmed devices are synced but orders are still missing from DataNow after an extended period.

When contacting support, please include:

• The venue name and DataNow URL
• The time data last appeared to update
• An approximate count of orders you believe are affected
• Any error messages displayed