fabro/docs/public/execution
Scott Werner e87130ae23 Require a server-managed environment for automations
Automations now store an environment_id that must reference an enabled
Docker or Daytona environment. Each trigger fire resolves the current
environment definition and snapshots its settings into the run, and
deleting an environment still referenced by an automation is rejected
with a conflict.

Existing automations are backfilled conservatively: a compatible
environment named default is selected when present, otherwise the sole
compatible environment. Anything ambiguous is left incomplete and cannot
run until an operator selects an environment in the web UI.

Scheduler failures are recorded on the automation as last_error and
cleared after the next successful scheduled run.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-30 09:58:13 -04:00
..
automations.mdx Require a server-managed environment for automations 2026-08-30 09:58:13 -04:00
checkpoints.mdx docs: sync product documentation 2026-07-24 11:39:16 -04:00
child-runs.mdx docs: add child runs guide 2026-05-25 15:43:53 -04:00
context.mdx fix(sandbox): materialize prompt blobs in runtime storage, not the checkout 2026-08-25 07:14:31 -04:00
environments.mdx Allow Daytona snapshots from Docker images 2026-08-27 15:02:50 -04:00
failures.mdx Add on_failure="succeed" as an explicit failure policy 2026-08-26 07:34:24 -04:00
observability.mdx docs: refresh product documentation 2026-08-24 09:53:09 -04:00
outcomes.mdx Add on_failure="succeed" as an explicit failure policy 2026-08-26 07:34:24 -04:00
run-configuration.mdx Allow Daytona snapshots from Docker images 2026-08-27 15:02:50 -04:00