Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/guides/tasks.md
Original file line number Diff line number Diff line change
Expand Up @@ -245,6 +245,7 @@ python main.py scheduler load-initial-schedule
```

> Remember, that if you do not explicitly import these, they will not be available to the scheduler.
> Importing schedules more than once will create duplicates.
### Manually executing tasks

When doing development, it is possible to manually make the scheduler run your task even if your Orchestrator instance is not in "scheduler mode."
Expand Down
23 changes: 17 additions & 6 deletions docs/guides/upgrading/4.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,17 +80,28 @@ The 4.7.0 migration will create the `apscheduler_jobs` table if missing, so upgr

### Who needs to take action?

**Users upgrading from 4.4–4.6:**
- Nothing special required; your scheduler data already exists.
Everyone who is upgrading to >= 4.7.0 needs to take action.
The following schedules will exist in the APScheduler database table:

**Users upgrading from <4.4 who used the old decorator:**
- Your schedules will not automatically reappear. Restore them by running:
-
task_resume_workflows
task_clean_up_tasks
task_validate_subscriptions

They will however be removed once the scheduler service starts and can no longer find these schedules in the codebase.

If you want to keep these schedules running, you will need to re-create them using the new Scheduler API.

- Re-create them by running:
```
python main.py scheduler load-initial-schedule
```
(More information: [Scheduler API](../tasks.md#the-schedule-api).)
Make sure your schedule definitions are imported so the scheduler can discover them.

**Users who never used the decorator:**
- No action required; the migration creates the table and you can add schedules normally.
- You still need to run the command above to ensure the old schedules are created in the database.
- the migration creates the table and you can add schedules normally via the API.


> Remember, that if you do not explicitly import these, they will not be available to the scheduler.
> Importing schedules more than once will create duplicates.