Manual workflow tasks
A manual task is a workflow step that cannot be completed automatically and that the workflow hands off to a specific person. Until the task is completed, the workflow waits at this step. That is why manual tasks are the place where automation "stops at a human", and they need to be handled with the same discipline as regular work tasks.
The manual task queue is available at /automation/workflows/tasks.
If a manual-task, instance, or rule card shows a technical ID instead of a name, status, or linked object, this is a display defect. Check the human title, status, assignee, and source; do not treat the raw ID as a working name or include the card in shared docs or screenshots. Send the screen to an administrator.
What a manual task is
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
When a workflow reaches a task node, it creates a manual task and addresses it to an assignee. The task describes what needs to be done, which object and process instance it relates to, and by what due date it is expected. The workflow will not move on until the assignee closes this step — completes or cancels it.
Where to handle them
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
The /automation/workflows/tasks section gathers the task queue. Use the title search, a state filter (pending, completed, or canceled), an assignee filter, or Only mine. The list itself puts pending and soonest-due tasks first; there is no separate due-date sort control. In the Tasks and CRM contexts, open the matching slice with the module parameter. It is useful for a manager to review the queue regularly: stuck tasks show where workflows are waiting on people.
What you see in a task
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
A task shows:
- name and description — what needs to be done;
- assignee — who the step is addressed to;
- due date — by what time the result is expected;
- linked object — a task, deal, or another work object;
- process instance — a link to the run within which the step was created;
- state — pending, completed, or canceled.
Before completing, look not only at the name but also at the linked object and instance: this shows which workflow the step is part of and why it is needed.
Complete a task
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
Complete a task only after the work has actually been done. After it is marked "completed", the workflow continues from the next step. Do not close a step formally "just so it doesn't hang" — this moves the workflow forward on false data and breaks the procedure further down the graph.
Cancel a task
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
If a step cannot or does not need to be completed, it is canceled. Canceling closes the task without completion; the workflow handles this according to its own logic. State why the step was canceled (in a comment on the linked object or to the workflow owner) — otherwise later it is unclear whether it was a decision or a mistake. Repeatedly canceling the same task is a signal that the template has the wrong trigger or recipient.
Queue and control
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
The task queue is a working control tool. When reviewing it, look at:
- who the assignee is and whether they are overloaded;
- whether tasks are overdue;
- whether a task on which the whole workflow stands is stuck;
- whether the same task keeps repeating because of a faulty template.
A stuck manual task is a common cause of a "stuck" process instance: the workflow is not broken, it is simply waiting for a person.
Technical identifiers
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
The queue or card may also show technical codes for the linked object or process instance, as well as unformatted status or type values. Use them only as a supporting reference: verify the human-readable title, assignee, and context instead of treating a code or enum as the work description. Do not copy such identifiers into task titles or public comments. If you see only a code or an unfamiliar value instead of clear context, stop and confirm the object with the workflow owner.
States and limitations
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
| State | What it means | What to do |
|---|---|---|
| Pending | The workflow stands at this step | Complete or cancel the task |
| Completed | The workflow has moved on | Nothing — the step is closed correctly |
| Canceled | The step is closed without completion | Check the reason in a comment on the object |
| Overdue | The due date has passed, the step is still open | Handle it immediately: check with the assignee or reassign |
| View only | No rights to handle it | Request access from the workflow owner |
Good practices
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
- Handle workflow tasks as carefully as work tasks.
- Complete a step only after real execution.
- When canceling, record the reason.
- Regularly review overdue and stuck tasks.
- Fix repeating or faulty tasks in the workflow template, not by hand.
Common mistakes
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
Closing a task formally. The workflow moves on with false data, and the error surfaces later.
Canceling without explanation. Later you cannot tell a deliberate decision from a mistake.
Not noticing stuck tasks. The whole workflow stands still because one step has not been handled.
Fixing the symptom by hand. If the same task keeps repeating, the problem is in the workflow template.
How to verify the result
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.
- after "completed", the process instance moved to the next step;
- canceled tasks have a clear reason;
- there are no unnoticed overdue and stuck steps in the queue;
- repeating faulty tasks have been resolved in the template.
Related scenarios
Manual task queue flow — conceptual flow, not a UI screenshot or evidence.