Executable Lifecycle
An executable combines code, args, profile, schedule, secret bindings, gas settings, runtime, and persistent storage. Open its detail page in Console → Executables, or use management commands and the API.
Executable states
| State | Meaning |
|---|---|
provisioning | Preparing the runtime and uploaded bundle. |
active | Enabled for scheduling and accepted invocation channels. |
paused | Scheduled runs are disabled; configuration and an eligible one-run permission override remain available. |
error | Provisioning or runtime recovery needs attention. |
deleted | Soft-deleted. |
Creating the executable provisions its runtime and then activates it if permissions are covered. Missing coverage leaves it paused without starting its schedule. A recurring enforcement issue can automatically pause an active executable; inspect pausedReason before resuming. Current enforcement tracking pauses after three consecutive recorded enforcement failures, not after every arbitrary task exception.
Actions
| Action | Effect |
|---|---|
| Execute now | Requests an additional real run of an active executable. |
| Attempt one run | An owner/admin explicitly overrides missing manifest coverage for a single manual attempt. Also available while paused; on-chain permissions still apply, and the schedule stays unchanged. |
| Simulate | Runs task logic and records a preview; no transaction, storage commit, or metered usage. |
| Pause | Disables further scheduled/active invocations; it does not undo an in-flight transaction. |
| Activate / Resume | Rechecks binding permissions and restores the schedule. |
| Delete | Soft-deletes a non-active executable, including paused, provisioning, or error states. Pause active work first. |
| Reprovision | Retries sandbox setup for an executable in error. |
| Regenerate sandbox | Recreates runtime resources; do not use sandbox-local files for durable data. |
| Switch function | Stages an active release in the same project while paused. |
Edit configuration
Args, schedule, secret bindings, gas settings, and supported same-chain profile assignments are editable. A target profile must be active and belong to the same project; profile migration and permission checks can block reassignment. Existing in-flight runs retain their original profile.
A release switch builds the replacement before committing the new function ID and args. While pending, conflicting args edits, activation, another switch, and manual regeneration are blocked. Success leaves the executable paused; failure leaves the old version committed with an error to inspect.
Through the API, PATCH /api/v1/executables/{id}/function returns 202 with a rebuilding request. Poll the resource until pendingFunctionSwitch clears, inspect any error, and activate deliberately. See release management.
Execution states are separate
Every invocation has its own timeline. submitted_unknown means a broadcast operation still has an unresolved outcome; it must not be treated as safely failed. skipped can represent a task decision, a preview, or a gate that prevented work, so read the reason.
For the complete execution status table, logs, and recovery checks, see monitoring.