User Manual
Help Center/User Manual/Task release: control when new tasks can start

Task release: control when new tasks can start

Last updated 2026-11-01

New tasks can be held back and released on a steady rhythm instead of all becoming work at once. Supervisors can also release a single task right away.

By default nothing changes: every new task can start right away, exactly as before. Release control only matters if your warehouse turns it on — for example to feed picking work to the floor in small, steady batches instead of one big wave all at once.

Set the release rhythm: Task Rules → Release#

  • Release strategy — Immediate: tasks can start as soon as they are created. Drip: tasks are released in small batches — pick how many minutes between batches and how many tasks per batch.
  • Direct release mode — when on, every new task is released immediately whatever strategy is set. Use it while you are setting things up, or if releasing ever gets stuck, so work never waits.
  • Release settings apply per warehouse (organization/warehouse level): the rhythm set here governs every task in the warehouse, whichever client it belongs to. Picking a client at the top of Task Rules stores a client-level value, but in this version client-level release rhythms are not applied yet — leave it on All to set the rhythm that actually takes effect.
  • Do not confuse this with customer priority weighting in dispatch order: there, a weight per client inside the (warehouse-level) dispatch policy does take effect — at the same urgency level, tasks of higher-weighted clients are dispatched first. That changes the order only; it does not give a client its own release rhythm.

A task that is not released yet cannot start#

A task waiting for release shows “Not released yet” on its detail page, and starting it shows a message explaining it has not been released. That is the rhythm working as set — the task will be released automatically when its turn comes.

Need one task right now? Release it manually#

  • From Task Query: unreleased tasks have a “Release now” button on their row.
  • From the task detail page: the same “Release now” button sits next to the release status.
  • The person assigned to the task gets a notification that it has been released and can start.
Tasks created before release control was set up are never held back — they were already released under the old way of working.