Provisioning Attempt

The Lifecycle

Transitions Explained

The request stores a pending attempt before starting execution. Publishing checks participant order, and the workflow processes construction, readiness and activation. Task refusals, exhausted retries and execution timeout can settle it failed; shared reconciliation also recovers missing execution. Success and failure communications have their own delivery limits.

What Cannot Happen

A terminal attempt is not resumed in place. Retry creates another attempt with a link and copied completed steps. The workspace cannot reopen through that retry until the remaining workflow and readiness succeed.

Concurrency and Timing

A partial unique index permits one open attempt per workspace. Participant work runs sequentially. Remote work can outlast the task deadline, so repeated invocation may overlap even where later calls converge. Execution has a seven-day bound; recovery depends on the shared job engine.