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

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

Fix this in detractor recovery playbook by acting on the exact problem first: trace this alert from response time to playbook start and name the queue or batch step that consumed the two days, replace that step with an immediate trigger, and time a test detractor end to end to prove same day start. 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 detractor recovery playbook started late - alert delayed - fix

Use this when

• The operation in detractor recovery playbook fails with this exact problem or symptom: NPS detractor recovery playbook started late - alert delayed - fix.
• 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 detractor recovery playbook, 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: trace this alert from response time to playbook start and name the queue or batch step that consumed the two days, replace that step with an immediate trigger, and time a test detractor end to end to prove same day start. 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 detractor recovery playbook 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 detractor recovery playbook 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

Delay hides in hand offs between systems, and a timestamp trace of one alert shows exactly which hand off holds detractors while others move through.

Variant phrasings

NPS detractor recovery playbook started late - alert delayed - fix

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 - how to fix NPS detractor recovery playbook started late error alert delayed two days fails error

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

detractor recovery playbook 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: detractor recovery playbook 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/pstrblAR9RhDBPWleWP75iEg

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

Thread query: how to fix NPS detractor recovery playbook started late error alert delayed two days fails error

TL;DR: Fix this in detractor recovery playbook by acting on the exact problem first: trace this alert from response time to playbook start and name the queue or batch step that consumed the two days, replace that step with an immediate trigger, and time a test detractor end to end to prove same day start. 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 detractor recovery playbook by acting on the exact problem first: move the playbook trigger from the daily batch report to the real time detractor alert, check the alert queue delay that held this one for two days, and add a same day escalation for any detractor alert older than your response target. 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 detractor recovery playbook started late - alert delayed two days

Use this when

• The operation in detractor recovery playbook fails with this exact problem or symptom: NPS detractor recovery playbook started late - alert delayed two days.
• 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 detractor recovery playbook, 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: move the playbook trigger from the daily batch report to the real time detractor alert, check the alert queue delay that held this one for two days, and add a same day escalation for any detractor alert older than your response target. 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 detractor recovery playbook 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 detractor recovery playbook 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 playbook waited on a batch job that only runs every two days, so the response clock started long after the customer gave the low score.

Variant phrasings

NPS detractor recovery playbook started late - alert delayed two days

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 detractor recovery playbook started late error alert delayed two days error failure

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

detractor recovery playbook 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: detractor recovery playbook 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_M7P5KEsRE0-sVXtKZUj4cg

Resolved from the public thread: https://vectle.com/posts/pst_M7P5KEsRE0-sVXtKZUj4cg

Thread query: NPS detractor recovery playbook started late error alert delayed two days error failure

TL;DR: Fix this in detractor recovery playbook by acting on the exact problem first: move the playbook trigger from the daily batch report to the real time detractor alert, check the alert queue delay that held this one for two days, and add a same day escalation for any detractor alert older than your response target. 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.