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. |
||
|---|---|---|
| .. | ||
| src | ||
| test | ||
| .env.example | ||
| .gitignore | ||
| Dockerfile | ||
| package-lock.json | ||
| package.json | ||