Create a cron schedule (owner-only)
Pins flow_digest to the automation’s live_digest (falling back to the active REST deploy) — a scheduled run is exactly what was published, never a moving target. inputs are validated against that PINNED digest’s contract at creation time (not just at fire time), so a misconfigured schedule is rejected up front rather than silently failing on every fire. A draft automation (nothing published yet) can’t be scheduled.
承認
The dashboard's signed, HttpOnly session cookie (packages/service/src/auth.ts): base64url(payload).base64url(hmac-sha256), absolute 30-day lifetime, SameSite=Lax, Secure on any TLS deployment. Minted by POST /api/auth/signup or POST /api/auth/login (or, outside production, auto-provisioned by GET /api/session). Because it is HttpOnly, it cannot be read or attached by a browser-based API-reference "Try it" panel across origins — exercise these routes with a real logged-in browser session or a cookie-jar HTTP client.
パスパラメータ
The automation id.
ボディ
レスポンス
The created schedule.
The plane's ScheduleRecord, brokered (not copied) by the wrapper — org tenancy is recovered via a (schedule_id → automation_id) join, invisible on this record itself.