Problem
The workflow execution page can crash while polling run details with:
Cannot read properties of undefined (reading 'status')
The stack points at the React Query refetchInterval callback in WorkflowExecution, where the code assumes query.state.data.workflowState is always present when query.state.data exists.
Why it matters
When this happens, the error boundary replaces the page with "Something went wrong" and users have to reload manually. This is especially disruptive for long-running workflows where the execution page is used to monitor progress.
Expected behavior
Polling should tolerate transient or malformed query state and continue rendering a loading/error state instead of crashing the entire route.
Proposed fix
Guard the nested query data access in the polling callback and fail explicitly if the run detail response has no run payload.
Validation
Validated locally with:
bun --filter @archon/web type-check
bun test packages/web/src/lib/select-initial-node.test.ts
Problem
The workflow execution page can crash while polling run details with:
The stack points at the React Query
refetchIntervalcallback inWorkflowExecution, where the code assumesquery.state.data.workflowStateis always present whenquery.state.dataexists.Why it matters
When this happens, the error boundary replaces the page with "Something went wrong" and users have to reload manually. This is especially disruptive for long-running workflows where the execution page is used to monitor progress.
Expected behavior
Polling should tolerate transient or malformed query state and continue rendering a loading/error state instead of crashing the entire route.
Proposed fix
Guard the nested query data access in the polling callback and fail explicitly if the run detail response has no
runpayload.Validation
Validated locally with:
bun --filter @archon/web type-check bun test packages/web/src/lib/select-initial-node.test.ts