Automation

QwenWorkAutomation with real limits

The interesting part is not that it can run on a schedule. It is that failures report which step broke, because an automation you cannot debug is an automation you switch off in week two.

What can start a run

The numbers that decide whether it fits

LimitValueConsequence
Runs per hour200 per workspaceA tight loop will hit it; batch jobs should be spread out
Active tasks, free10Enough to test, not enough to run a department
RetriesAutomatic for transient failuresA deterministic failure will retry and then stop
ConcurrencyTask-dependentTwo runs writing the same file will collide

Designing one that survives

  1. Start manual

    Build it as a button. Watch it run ten times before you put it on a schedule.

  2. Make the output idempotent

    If the task reruns, it should overwrite the same file or append a dated one — never duplicate rows into a summary.

  3. Write the failure path first

    Where does the output go when the input is malformed? A task with no failure path fills a folder with broken documents.

  4. Add an owner

    Every automation needs a person who reads its failures. Orphaned automations fail silently for months.

Do not automate a decision you have not made manually ten times. Automation freezes a process. If the process is still changing weekly, you are freezing the wrong version of it.
Automation output usually lands in the workspace. Permissions decide who sees it.