Troubleshoot Task work
Read the explanation attached to the unavailable action or failed request first. The same Task can offer different actions to different users, and those rights can change while a page is open. Refreshing reads current rights; it does not grant new ones.
| Symptom | Check and next action |
|---|---|
| Tasks or a configuration catalog is missing | Ask the administrator to check module state, Runtime Menu assignment and the appropriate read permission. Menu setup alone grants no rights. |
| Cannot create from a Definition | Check Creator mapping, active Definition, required Due/Context/Input Data and admitted Owner/Responsible. Configuration Management alone is insufficient. |
| Worker is absent from a picker | Check an active Worker linked to an active User, participant or Queue admission, and current record visibility. Changing a display name does not fix an identity association. |
| No candidate or Give me work returns No work | Check mode, effective membership, availability, eligibility, global/Queue capacity and working time when enabled. A hidden or future backlog does not promise an eligible task now. |
| Give me work reports capacity | Finish or lawfully release existing work, or have an authorized configurator review the limit. Rechecking the old request cannot allocate another task. |
| Start is unavailable | Assignment is not Start. Check the current performer, transition, active identity and execution capacity. Due date passing does not Start or complete work. |
| Change queue is refused | Remove the Executor explicitly when required; the task must have no active execution and be in a supported state. Check destination lifecycle/admission and Change queue rights. |
| Return is unavailable | The Queue may forbid an Executor’s voluntary return. An authorized dispatcher or Task administrator must use explicit release. |
| Complete is refused | Check transition and Outcome grants, current required data, completion comment/evidence and the selected Outcome’s requirements. Saving a draft is not completion. |
| A save reports a stale version | Reload current values and reconcile the draft. A deliberate revised command is a new intent; do not keep resubmitting stale versions. |
Unknown request outcomes
Section titled “Unknown request outcomes”If a connection is lost after submitting a command, use the offered check or retry flow for the same request. Starting another create or assignment request can create another effect. A pending Queue request continues after closing the dialog. Reopen/check that request before deciding to make a new request.
A terminal request whose task is now unavailable can represent a committed assignment that you no longer may read. It is not evidence that the assignment failed. Ask an authorized dispatcher to inspect current work when necessary.
Content and instructions
Section titled “Content and instructions”Task access and Context access are separate. Missing Collaboration content can reflect disabled channels, source-specific rules, a changed Context or loss of access to the owning Entity/Board. A Task role does not override that resource. If a configured publication destination is unavailable, sending can be refused; the system does not silently publish somewhere else.
Instruction files are read through the Task’s current Definition binding. An old link may stop working after a binding is removed. That is different from requiring the Worker to browse the source File Storage folder.
Delayed signals
Section titled “Delayed signals”Open the signal details and distinguish its source condition from Inbox read, archive, snooze and acknowledgement. Acknowledgement does not resolve an overdue task or clear a block. Use the ordinary Task actions to address the cause.
Signal evaluation runs in the background. A temporarily delayed Worker resumes pending evaluation after recovery. Administrators can inspect pending age, backlog and processing failures in Monitoring. Repeatedly editing a Task is not needed to force delivery. Check recipient access and configured notification transitions if a visible signal does not produce an Inbox notification.
If a Worker’s user link is removed or deactivated, assignments are retained while the old session loses authority. Use explicit authorized recovery of the work. Relinking a user does not fabricate execution events or erase history.