Affects
Teams running Flowker workers with scheduled workflows enabled.
What changed
The documentation now correctly states that the scheduler uses its own Redis configuration, separate from the configuration for multi-tenant lifecycle events. Startup does not enforce that the two configurations use different Redis instances or logical database indexes. Operators must point the scheduler to a dedicated Redis instance or, when sharing an instance, configure a logical database index that tenant lifecycle events do not use. This is a documentation correction; runtime behavior did not change.
Impact
Classification: Action required. The former wording implied that the scheduler was already isolated. Isolation is an operator configuration responsibility, so teams must verify it rather than relying on startup to provide it.
What you need to do
1
Review the scheduler Redis settings for every worker that runs scheduled workflows.
2
Use a dedicated Redis instance for the scheduler, or set
SCHEDULER_REDIS_DB to a logical database index separate from tenant lifecycle events.3
Confirm the configuration before enabling or continuing to run scheduled workflows.