warpdotdev/warp · error
Error polling OAuth status: {err}
Error message
Error polling OAuth status: {err} What it means
The spawned poll future for the OAuth connect transaction returned Err (app/src/ai/agent_sdk/agent_config.rs:183 Err arm); the message interpolates the error with inline {err} via anyhow. This is a transport/API-level failure of the polling itself, distinct from any transaction status.
Source
Thrown at app/src/ai/agent_sdk/agent_config.rs:183
ctx.terminate_app(
TerminationMode::ForceTerminate,
Some(Err(anyhow::anyhow!(
"GitHub authorization expired. Please try again."
))),
);
}
Ok(_) => {
ctx.terminate_app(
TerminationMode::ForceTerminate,
Some(Err(anyhow::anyhow!(
"Unexpected OAuth status"
))),
);
}
Err(err) => {
ctx.terminate_app(
TerminationMode::ForceTerminate,
Some(Err(anyhow::anyhow!(
"Error polling OAuth status: {err}"
))),
);
}
}
});
}
(Some(auth_url), None) => {
println!("\nAuthorize access here: {auth_url}\n");
println!("After authorizing, please re-run this command.");
ctx.terminate_app(TerminationMode::ForceTerminate, None);
}
_ => {
ctx.terminate_app(
TerminationMode::ForceTerminate,
Some(Err(anyhow::anyhow!(
"Cannot list agents: authorization required but no auth flow provided"
))),View on GitHub (pinned to e72fd7aacb)
Solutions
- Check connectivity and re-run the command
- Retry once — transient polling failures commonly clear
- If persistent, read the embedded {err} text to see which request failed and check service status
Defensive patterns
Strategy: retry
Prevention
- Treat OAuth polling errors as transient; retry the command once before investigating
- Keep the auth window short so fewer polls are exposed to network flakiness
When it happens
Trigger: Network drop while polling the OAuth connect tx status; the GraphQL endpoint returning an error payload or 5xx while the browser flow is still pending.
Common situations: Flaky connectivity mid-auth; brief server-side errors during deploys; proxies killing long-polling requests.
Related errors
- Exceeded maximum number of authorization attempts ({}). Plea
- GitHub authorization failed. Please try again.
- GitHub authorization expired. Please try again.
- Cannot list agents: authorization required but no auth flow
- Invalid repo format: '{}'. Expected 'owner/repo' or 'https:/
AI-assisted analysis of warpdotdev/warp@e72fd7aacb (2026-08-16).
Data as JSON: /api/errors/5e0ff892e38f6cc7.
Report an issue: GitHub.