Prepare a diagnosis when a scheduled data refresh fails
After normal retries fail, inspect the affected integration and related projects to give responders useful evidence and next steps.
How this works
After normal retries fail, inspect the affected integration and related projects to give responders useful evidence and next steps.
Investigate a refresh only after the defined retry policy has been exhausted. Compare failure signatures across permitted integrations to distinguish local configuration problems from shared incidents while avoiding disclosure of another client’s data.
Before you start
Defined operating scope
Scheduled data jobs sometimes fail despite retries and need a contextual diagnosis.
Required source material
Obtain Refresh failure and logs; Retry status; Related integration context and ownership. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
Normal retry is still in progress. Observe its outcome instead of starting a competing repair.
Prepare the inputs
- refresh_run
- Required
Run ID, integration and failure time
Preserve original error and affected period.
- retry_history
- Required
Attempts and outcomes
Confirm retries are exhausted under the policy.
- related_status
- Required
Permitted integration health metadata
Use metadata rather than unrelated client payloads.
- owner_routes
- Required
Source and platform owners
Identify who can perform the next check.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check refresh_run, retry_history, related_status, owner_routes before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected refresh_run and any missing required fields.
Trigger investigation after the defined retry policy is exhausted
- Confirm the failed run and retry history so investigation does not compete with an active normal retry.
- Verify retry exhaustion and last-success timestamps from run history.
Checkpoint: A saved intermediate result for: Trigger investigation after the defined retry policy is exhausted.
Inspect the failure and compare related projects
- Inspect error class, last successful refresh and configuration changes, retaining exact evidence rather than paraphrasing away useful codes.
- Check that cross-project comparisons use only permitted operational metadata.
Checkpoint: A saved intermediate result for: Inspect the failure and compare related projects.
Separate a client-specific issue from a possible shared failure
- Compare permitted related-run metadata for timing and signature, separating client-specific symptoms from possible shared failure.
- Verify retry exhaustion and last-success timestamps from run history.
Checkpoint: A saved intermediate result for: Separate a client-specific issue from a possible shared failure.
Notify the relevant owners with evidence and proposed checks
- Prepare an incident brief for the appropriate owners with impact, uncertainty and a bounded next diagnostic step.
- Check that cross-project comparisons use only permitted operational metadata.
Checkpoint: A saved intermediate result for: Notify the relevant owners with evidence and proposed checks.
Package the result and unresolved work
- Do not treat a plausible diagnosis as confirmed. Keep cross-client information restricted and require approval for production repairs.
- Diagnosis is read-only and does not authorize credential changes or production repairs.
Checkpoint: An incident brief for the responsible analyst or engineer. Unresolved items remain visible in the review record.
Decisions along the way
Normal retry is still in progress.
Observe its outcome instead of starting a competing repair.
Several integrations fail with the same signature.
Escalate a shared-incident hypothesis without exposing client-specific records.
A repair would mutate production configuration.
Prepare the evidence and proposed change for the authorized owner; do not apply it as diagnosis.
What you will produce
failed-data-refresh-diagnosis-result.json
JSONAn incident brief for the responsible analyst or engineer. Label proposed and completed states separately.
Include: run_id · affected_period · retry_state · failure_signature · related_health · hypotheses · owner_next_check · status · evidence_reference · review_note
failed-data-refresh-diagnosis-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving owner_routes.
Include: source_reference · question · owner · next_action
Check the result
- Verify retry exhaustion and last-success timestamps from run history.
- Check that cross-project comparisons use only permitted operational metadata.
- Inspect refresh_run and retry_history in both the original and output; confirm that record identity and interpretation survived the transformation.
- Do not treat a plausible diagnosis as confirmed. Keep cross-client information restricted and require approval for production repairs.
When something goes wrong
Normal retry is still in progress.
Observe its outcome instead of starting a competing repair. Retain the affected evidence and recovery status.
Several integrations fail with the same signature.
Escalate a shared-incident hypothesis without exposing client-specific records. Retain the affected evidence and recovery status.
A repair would mutate production configuration.
Prepare the evidence and proposed change for the authorized owner; do not apply it as diagnosis. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Prepare a diagnosis when a scheduled data refresh fails for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Run R-8 exhausts three configured retries with token-expired errors. Other permitted integrations refreshed successfully during the same window.
Expected result
Synthetic expected result: Brief favors a local authentication issue and asks the integration owner to verify credential expiry. It does not claim a platform outage or renew credentials automatically.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure time to an owner-reviewed diagnosis; incorrect causes or unnecessary escalations.
Stop or revise
A repair would mutate production configuration. Pause affected records and apply this recovery: Prepare the evidence and proposed change for the authorized owner; do not apply it as diagnosis.
Keep the scope clear
- Diagnosis is read-only and does not authorize credential changes or production repairs.
- A plausible explanation remains a hypothesis until the owner verifies it.
Check before using
Do not treat a plausible diagnosis as confirmed. Keep cross-client information restricted and require approval for production repairs.
Business activities
- Review business performance
- Keep digital services running
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Refresh failure and logs · Retry status · Related integration context and ownership
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow