> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Flowker scheduler Redis isolation configuration

> Flowker scheduler Redis isolation is configured by the operator, not enforced at startup.

<Badge stroke icon="calendar-days" iconType="regular">August 10, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation correction</Badge> <Badge color="red" size="lg" stroke icon="triangle-exclamation" iconType="regular">Action required</Badge>

## 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

***

<Steps>
  <Step>
    Review the scheduler Redis settings for every worker that runs scheduled workflows.
  </Step>

  <Step>
    Use a dedicated Redis instance for the scheduler, or set `SCHEDULER_REDIS_DB` to a logical database index separate from tenant lifecycle events.
  </Step>

  <Step>
    Confirm the configuration before enabling or continuing to run scheduled workflows.
  </Step>
</Steps>

### Deadline

No product-imposed deadline. Validate the isolation before you enable or continue operating scheduled workflows.

## Resources

***

* [Flowker environment variables](/en/flowker/flowker-environment-variables)