Diego ImbertandClaude Opus 5 e3c0f532ff fix(schedules): record the deployed enabled state however the editor opened ...

The reading sat inside the branch that captures a baseline, so a schedule opened
with a config handed in — the trigger panel of a script or flow — never took
one, and a save there settled against whatever the last open had left. Both ways
in hold the deployed state on the form at that point, which is what the reading
is about.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KcyBRxE8j3ujCYkum9KrC4

2026-09-06 16:08:36 +02:00

..

lib

fix(schedules): record the deployed enabled state however the editor opened

2026-09-06 16:08:36 +02:00

routes

fix(schedules): take the deployed enabled state from the deployed config alone

2026-09-06 15:47:24 +02:00

.d.ts

…

.gitkeep

…

app.d.ts

…

app.html

feat(apps): opt-in sandbox isolation for published & raw apps (alpha) (#9420)

2026-06-23 10:05:00 +02:00

global.d.ts

raw apps v2 (#7251)

2025-11-29 01:23:47 +00:00

hooks.ts

…

types.d.ts

…