The scheduler tick loop updates a schedule's status to 'starting' and 'stopping' in the database while it initiates the API calls to the recorder container. The original CHECK constraint in recorder_schedules rejected these two statuses, causing the scheduler to crash on constraint violation and never start the job. |
||
|---|---|---|
| .. | ||
| migrations | ||
| pool.js | ||
| schema.sql | ||
| schema_patch_ampp.sql | ||
| schema_patch_editor.sql | ||
| schema_patch_groups_tokens.sql | ||