Claiming & Submitting Work

Tasks page

Contributors access their work from the Tasks page in the sidebar. It has two tabs:

• Available Tasks — subtasks and reviews available to claim, plus any tasks already claimed by the contributor. Stat cards at the top show available and claimed counts.
• Submitted Tasks — history of completed submissions.

The Tasks page can be scoped to a specific project or viewed globally across all projects.

Claiming tasks

1. Navigate to the Available Tasks tab.
2. Browse available tasks. Each row shows the pipeline name, project, node name, and status.
3. Click Claim to take ownership of a task.

Contributors only see tasks they are eligible to claim based on their role and pipeline configuration.

Claim limits

Pipelines can be configured with claim limits per contributor role. If a contributor reaches their limit, the Claim button is disabled and a banner shows how many tasks are claimed out of the allowed maximum. The contributor must submit or release an existing task to claim more.

Claim timeout

Admins can configure a claim timeout per pipeline. If a contributor holds a claimed task beyond the timeout period, the task is automatically released back to the available pool.

Completing a task

1. Click on a claimed task to open the task form.
2. The form may include a Context section containing fields from previous nodes. These may be read-only or editable depending on the pipeline configuration.
3. Fill out the required fields and generate LLM responses as needed.
4. Click Submit.

What happens after submission

Depending on the pipeline structure:

• If the next node is a review node, the submission enters a reviewer's queue.
• If the next node is a logic gate, conditions are evaluated automatically and the task is routed.
• If the next node is another subtask, it becomes available to be claimed.
• If the next node is an end node, the task is marked as finished.

Releasing a task

If a contributor has claimed a task but cannot complete it, they can click the unlock icon on the Available Tasks table to release it back to the pool.

Rework

If a reviewer rejects a submission, the task may be sent back for rework:

1. The task reappears on the Available Tasks tab with a Returned badge. Depending on the rejection routing mode, it may be assigned back to the same contributor or made available to others.
2. The contributor can view the reviewer's feedback and rejection reason on the task form.
3. The contributor can view the version history of each field, showing previous submissions and why they were rejected.
4. The contributor can then edit the submission and resubmit.

The number of rework cycles is limited by the pipeline's re-review limits. If the limit is exceeded, the task is quarantined or escalated for admin intervention.