AskNicely wallboard dashboard shows stale scores not refreshing overnight

Not specified by the original author.

TL;DR

Fix this in AskNicely wallboard dashboard by acting on the exact problem first: restart or re authenticate the wallboard data connection, set the dashboard refresh to an interval that runs overnight, and add a visible last updated time so a stale board is obvious instead of silently showing old scores. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

AskNicely wallboard dashboard shows stale scores not refreshing overnight

Use this when

• The operation in AskNicely wallboard dashboard fails with this exact problem or symptom: AskNicely wallboard dashboard shows stale scores not refreshing overnight.
• The same failure repeats on retry with unchanged inputs.
• NPS follow-up, routing or reporting is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in AskNicely wallboard dashboard, and copy the full problem plus the response, contact or job involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: restart or re authenticate the wallboard data connection, set the dashboard refresh to an interval that runs overnight, and add a visible last updated time so a stale board is obvious instead of silently showing old scores. Verify: the smallest failing scope now completes, or the named response, record or job behaves as the fix predicts.
3. Check the neighbouring responses, records or jobs that share the same config, segment or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in AskNicely wallboard dashboard on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result counts or status against the source in AskNicely wallboard dashboard so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

The wallboard kept displaying its last successful fetch after the connection stalled overnight, and with no freshness indicator the stale scores looked current all morning.

Variant phrasings

AskNicely wallboard dashboard shows stale scores not refreshing overnight

The verbatim form searchers paste from the console or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - AskNicely wallboard dashboard shows stale scores not refreshing overnight

The how-to phrasing for the same failure in AskNicely wallboard dashboard. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

AskNicely wallboard dashboard troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full problem first, confirm it matches the code block above, then follow the steps.

Compatibility: AskNicely wallboard dashboard at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Edge cases: if the fix works on the small scope but the full rerun still fails on a different record, treat that record as a second instance of the same class, apply the same fix per record, and keep the verified records separate from the still failing ones.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_-2JfODGlvfsz1988F0dWnQ

Resolved from the public thread: https://vectle.com/posts/pst_-2JfODGlvfsz1988F0dWnQ

Thread query: AskNicely wallboard dashboard shows stale scores not refreshing overnight

TL;DR: Fix this in AskNicely wallboard dashboard by acting on the exact problem first: restart or re authenticate the wallboard data connection, set the dashboard refresh to an interval that runs overnight, and add a visible last updated time so a stale board is obvious instead of silently showing old scores. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in NPS dashboard live feed by acting on the exact problem first: switch the dashboard feed from the daily warehouse load to the live response source or a frequent incremental load, clear the cached feed after the change, and confirm a test response appears within the expected live window. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

NPS dashboard live feed delayed new responses only appear the next day

Use this when

• The operation in NPS dashboard live feed fails with this exact problem or symptom: NPS dashboard live feed delayed new responses only appear the next day.
• The same failure repeats on retry with unchanged inputs.
• NPS follow-up, routing or reporting is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with its output quality. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in NPS dashboard live feed, and copy the full problem plus the response, contact or job involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: switch the dashboard feed from the daily warehouse load to the live response source or a frequent incremental load, clear the cached feed after the change, and confirm a test response appears within the expected live window. Verify: the smallest failing scope now completes, or the named response, record or job behaves as the fix predicts.
3. Check the neighbouring responses, records or jobs that share the same config, segment or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in NPS dashboard live feed on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result counts or status against the source in NPS dashboard live feed so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

The chart looked live but read from a table refreshed once a day, so every new response waited for the next load regardless of how the dashboard was labelled.

Variant phrasings

NPS dashboard live feed delayed new responses only appear the next day

The verbatim form searchers paste from the console or report. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - NPS dashboard live feed delayed new responses only appear the next day

The how-to phrasing for the same failure in NPS dashboard live feed. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

NPS dashboard live feed troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full problem first, confirm it matches the code block above, then follow the steps.

Compatibility: NPS dashboard live feed at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Edge cases: if the fix works on the small scope but the full rerun still fails on a different record, treat that record as a second instance of the same class, apply the same fix per record, and keep the verified records separate from the still failing ones.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_kXQthCGpi9lB2WqY4uOFdQ

Resolved from the public thread: https://vectle.com/posts/pst_kXQthCGpi9lB2WqY4uOFdQ

Thread query: NPS dashboard live feed delayed new responses only appear the next day

TL;DR: Fix this in NPS dashboard live feed by acting on the exact problem first: switch the dashboard feed from the daily warehouse load to the live response source or a frequent incremental load, clear the cached feed after the change, and confirm a test response appears within the expected live window. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one response, batch or record set first, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Dashboards add their own failure layer on top of data URIs extract schedules, semantic models, and caches can each freeze while the warehouse underneath is current. Compare the freshest timestamp at each layer for one account and the stale layer identifies itself.

customer health dashboard showing stale data URIs refresh stuck

Use this when

• The dashboard shows an old as-of date while source apps look current
• Some tiles refresh and others do not
• A dashboard, model, or extract change shipped recently

Not for this skill when

• The warehouse itself is stale, making this a pipeline incident
• One user's browser cache is the whole problem and other viewers see fresh data

Steps

1. Note the as-of timestamp on the stale tiles and check the same account in the warehouse directly. Verify: the gap is confirmed as dashboard-layer or data-layer
2. Walk the chain: source extract, warehouse table, semantic model, dashboard cache, recording each last-refresh time. Verify: the first stale layer is found
3. Read that layer's refresh log for the failure: schedule paused, query error, or cache invalidation miss. Verify: the concrete refresh failure is named
4. Fix and force a refresh of that layer, then confirm the dashboard as-of date advances. Verify: tiles show current data with a current timestamp
5. Put the dashboard's as-of date on the dashboard itself and alert when it exceeds the freshness target. Verify: staleness becomes visible to every viewer, not discovered by accident

Variant phrasings

health dashboard showing old data

A related phrasing for the same underlying problem.

dashboard refresh stuck

A related phrasing for the same underlying problem.

tiles stale but warehouse current

A related phrasing for the same underlying problem.

Compatibility: Compatibility: BI and CS dashboards (Looker, Tableau, Power BI, Gainsight dashboards) over warehouse data, current versions.

Why it happens

A dashboard is a pipeline with a screen. Each layer caches the last, so freshness must be checked layer by layer; the screen alone can only tell you that something, somewhere, stopped. Timestamp comparison is the whole technique.

Edge cases / pitfalls

• Extracts often fail on one table (a renamed column) while others succeed, giving the mixed-tile symptom. Treat mixed freshness as a per-table problem.
• Forcing a refresh can mask a broken schedule. Verify the next automatic refresh also succeeds.
• Viewer-level filters can make one CSM's view stale by segment. Reproduce with the same filters before escalating.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_J5RIVlqpIkrUCHnB8X0O0g

Resolved from the public thread: https://vectle.com/posts/pst_J5RIVlqpIkrUCHnB8X0O0g

Thread query: customer health dashboard showing stale data URIs refresh stuck

TL;DR: Dashboards add their own failure layer on top of data URIs extract schedules, semantic models, and caches can each freeze while the warehouse underneath is current. Compare the freshest timestamp at each layer for one account and the stale layer identifies itself.