Skip to main content

​
Inbox and trigger delivery

config.automation.defaultDeliveryMode decides how Events, Schedules, and Agent handoffs enter the Agent when the trigger does not override it: The create form defaults to INBOX.

​
Inbox item fields

Use a deterministic de-duplication key for retried webhooks and recurring producers, for example invoice:2026-09:customer-42.

​
Direct run fields

A direct run requires instruction and can include:
  • triggerType, triggerRefType, and triggerRefId for correlation;
  • scheduleFor as an ISO timestamp with timezone or Unix milliseconds, up to 30 days ahead;
  • a JSON state object for run-scoped context;
  • up to 32 additional pluginIds.
Do not use run state for secrets or durable files. Keep secrets in Secrets and persistent output in the Agent workspace. A delayed direct run is visible immediately as CREATED, with scheduledFor in its details. It does not occupy an execution slot while waiting for its initial time. Once due, it must pass the Agent’s concurrency gate; waiting for capacity is PENDING with a capacity wait reason. Later continuation wake times are separate from the original accepted schedule.
Use scheduleFor for both Inbox and direct runs. A past public timestamp or one more than 30 days ahead is rejected. An already accepted request that reaches dispatch after its time becomes immediately eligible; eligibility is not a promise of an exact start time.

​
Delegation and limits

Limits can be present in both config and policy. For concurrency and child limits, the lower configured or policy value wins. policy.maxTicks overrides config.maxTicks. merge_partial is effective when selected in either layer; otherwise failure mode is fail_parent. Start with one root run and two concurrent children. Increase concurrency only after the service account, downstream rate limits, idempotency, and output-merge behavior have been tested.

​
Managed automation settings

Automation policy can define how approval-required work is escalated and how managed notifications are delivered. These settings record operator intent; they do not bypass runtime approval policy, identity, or target access. Treat advanced automation fields as managed configuration and validate the current OpenAPI schema before generating them programmatically. Continue with agent configuration.
Last modified on November 8, 2026