Apply

Resume a stuck deploy operation

Re-run the failed phase forward when the operation is in activation_pending or schema_settling. Migrations are NEVER replayed. NOT lifecycle-gated — completes already-authorized in-flight work.

post/apply/v1/operations/{operation_id}/resume

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/apply/v1/operations/{operation_id}/resume
  • Auth: API key in header SIGN-IN-WITH-X

Path parameters

operation_idstring required

Operation ID

Headers

SIGN-IN-WITH-Xstring required

SIWX auth header — base64-encoded JSON payload containing a signed CAIP-122 (EIP-4361) message. See https://docs.x402.org/extensions/sign-in-with-x.

Response

Operation snapshot after resume attempt.

operation_idstring required
release_idstring nullable required
status'planning' | 'uploading' | 'committing' | 'staging' | 'gating' | 'migrating' | 'schema_settling' | 'activating' | 'activation_pending' | 'needs_repair' | 'ready' | 'failed' | 'rolled_back' required
urlsobject

site is the project's public URL, present when the project owns at least one subdomain. console is the project's page in the console (https://console.run402.com/orgs/{org_id}/projects/{project_id}), present exactly when site is present; a function-only project with no site carries no console key either.

snapshot_skipped_reasonstring nullable

Present when pre-migration snapshotting was intentionally skipped or downgraded, for example because the project exceeded the snapshot size threshold.

Example response

{
  "next_actions": [
    {
      "method": "POST",
      "path": "/tiers/v1/hobby",
      "auth": "x402"
    }
  ],
  "restore_point": {
    "restore_url": "/projects/v1/prj_.../snapshots/snap_.../restore",
    "command": "run402 snapshots restore prj_... snap_..."
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.