Diagnose missing data
Check scope, collection state, filters, and access conditions to distinguish missing data from failures.
When to use this workflow
“The report is empty. Is collection still running, or is something broken?”
Before fetching
Record the command, workspace, prompt, platform, period, and last known result. Preserve the original error or empty response before retrying.
Complete the CLI quickstart and confirm the workspace with orc workspace current --json. Replace example IDs, URLs, dates, and settings. Apply only approved mutations.
1. Check scope and prompt configuration
First check workspace selection, disabled or archived prompts, and platform or region mismatches.
orc workspace current --json
orc status --json
orc prompts get YOUR_PROMPT_ID --json2. Compare the filtered result with recent answers
Read answers for the same prompt and workspace, then check whether the original dates or filters exclude them. Usage totals alone do not establish a contractual limit.
orc answers list --prompt-id YOUR_PROMPT_ID --json
orc usage get --json3. Classify only the state the evidence supports
If answers appear under different conditions, the original filter excluded them. Confirm pending collection, limits, or failures only from explicit state or error evidence. An empty result alone leaves the cause unknown; identify the missing collection history.
Deliverable
Deliver the supported diagnosis, settings and responses with timestamps, and the next check. Keep insufficient permissions separate from no data.
On fetch failure, retain the error and request scope. Do not count empty data, incomplete pagination, or missing permissions as a completed investigation.
Next steps
If a failure remains, report it and verify the fix, including this workflow and the failed step.