Documented steps

Every mutating call (POST/PATCH/DELETE on projects, branches, endpoints...) returns an 'operations' array with id, action, and status
Poll GET https://console.neon.tech/api/v2/projects/{project_id}/operations/{operation_id} on ~5-second intervals
Statuses: scheduling, running, finished, failed, cancelling, cancelled, skipped — stop polling at finished/skipped/cancelled
A single call can return multiple operations (e.g. create_branch + start_compute); wait for all of them when subsequent calls depend on the result
If any API call returns 423 Locked, the project is busy — retry the same request with exponential backoff (e.g. 0.1s, doubling)

Known gotchas

'failed' is NOT a terminal status in the docs' sense of completion — a failed operation does not advance and may need a manual retry of the original request
The API can return the operation as 'scheduling' even after a 201/202 — do not assume readiness from the HTTP status alone
Old operations may be pruned from the API — persist your own history if you need long-term audit
Official docs: https://neon.com/docs/manage/operations | https://neon.com/docs/reference/api/operations

developers.google.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Poll Neon API operations for completion after mutating calls to avoid race conditions

Documented steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?