If there are multiple workers, The scheduler can also start multiple times, causing duplicate execution. How to improve and avoid

[kanbang]

If there are multiple workers, The scheduler can also start multiple times, causing duplicate execution.
How to improve and avoid

[kanbang]

uvicorn app.main:app --workers 3

[VannySothea]

If there are multiple workers, The scheduler can also start multiple times, causing duplicate execution. How to improve and avoid

Thank you for reporting this issue! The behavior you're experiencing happens because, in a multi-worker environment, each worker starts its own instance of the scheduler, leading to duplicate task execution.

This is a common challenge in applications using schedulers with multiple workers. Here are some ways to address it:

1. Run the scheduler in a separate, dedicated process (e.g., using Celery or APScheduler as a standalone service).
2. Use a distributed lock (e.g., Redis-based locking) to ensure only one worker executes the scheduled tasks.
3. Use a task queue to decouple task scheduling and execution.

I will update the documentation to include these best practices.