Skip to main content

Scheduled tasks

A scheduled task is warehouse work the system does by itself, at the times you set, with nobody at a screen. You describe once what should happen and how often — every hour, on Saturday mornings, once every second month — and from then on it happens without you.

Scheduled tasks live in the client app, under Administration → Scheduled tasks.

What runs on a schedule​

Cycle counting — the system finds the cells whose count is due and creates a count document for each of them. This is the operation you can set up today; what it decides for itself and what you decide for it is described in Cycle counting.

The module is meant to take over the other regular chores of a warehouse as well. These are next in line, and none of them can be set up yet:

  • Returning free stock from the shipping area. Goods that came back after a cancelled dispatch, or were left over by a partial one, stand in the shipping area where picking cannot reach them. The task finds the part that is free — not reserved by anything — and sends it back into storage.
  • Putting away containers from the staging areas. Containers parked in a receiving or shipping area with no operation left to move them are sent on to storage cells.
  • Replenishing pick faces, planning waves, generating putaway — announced, further out.

One task type, many instances​

Every row in the list is a separate instance: its own name, its own schedule, its own settings. That is the point of the list — the same operation can run several ways side by side.

Cycle counting shows it best. One instance goes round every hour and takes only the cells the system has flagged as doubtful. A second walks the empty cells once every two months. A third covers a single storage zone on Saturday mornings. Three instances, one type of task.

Which is why the name matters more than it looks: it is what later tells you which instance produced the documents in front of you. A task will not be saved without a name, and no two of your tasks may share one.

Whose documents these are​

Every instance names the user it runs as, and the documents it creates carry that user as their author. A scheduled count therefore looks exactly like a count that person planned — nothing on the document says a schedule made it. Pick a user whose name will make sense to whoever opens those documents later.

Pausing a task​

An instance can be switched off. It stays in the list with its schedule and settings untouched and simply stops firing — which is what you want when an operation should pause for a while rather than be set up again from scratch afterwards.

Where to go next​