Creating new Recurring Tasks only happens on second release

[matthewelwell]

Describe the bug

When a new recurring task is added to the application, it will not be created on the first deployment that occurs. This is because, during the canary deployment, the new tasks will create the task in the database on startup, but the existing task processor units will delete it as it doesn't exist in their registry.

See relevant code here.

To Reproduce

Steps to reproduce the behavior:

1. Create a new Recurring Task.
2. Deploy the application to ECS.
3. Notice that the new task does not exist in the task_processor_recurringtask table.

Expected behavior

The recurring task is created in the database by the new deployment.

Screenshots

N/a

How are you running Flagsmith?

• Self Hosted with Docker
• Self Hosted with Kubernetes
• SaaS at flagsmith.com
• Some other way

Additional context

N/a