How Do I Complete a Human Review Task in Dave by voolama?

Summary

The steps

1. 1

   Open the Task Inbox and find your task

   The Task Inbox is the central view for all tasks assigned across your tenant in Dave by voolama (hellodave.ai). It is available to Admin and Use roles only. Sourced from the tasks help documentation, DEV v0.11.0, confirmed against content_orchestrator main at commit ddb945f, 2026-08-30.

   Do this

   1. Navigate to Tasks in the sidebar. The page displays the heading Task Inbox.
   2. Use the status filter dropdown in the top-right corner. Set it to pending to see only tasks that need your attention.
   3. Read the task table: Type (task category, linked to detail page), Status (colour-coded badge), Instance (truncated parent instance ID), Assignee (your user ID or a dash if unassigned), and Due (deadline or a dash if not set).
   4. Prioritise tasks with a due date. The tasks help documentation states: "Tasks with a due date may time out and fail if not completed in time."
   5. Click the Type link on the task you want to complete to open the task detail page.

   Example

   You log in and see three tasks. The filter is set to All Statuses. You switch it to pending. Two remain: one human_review due tomorrow, one agent_review with no due date. You click the human_review Type link first because it has the earlier deadline.

   Best practice

   • Check the Task Inbox at the start of each working session. Pending tasks block workflow progress: the sooner you act, the faster instances complete.
   • If the Task Inbox is empty after setting the filter to All Statuses, call GET /api/tasks in browser developer tools. An empty array confirms no tasks exist for your workspace. Navigate to Instances and check the Running Instances count.
   • If you cannot see the Tasks sidebar link, call GET /api/tasks with your session token. A 403 response with the missing permission named (tasks:read) confirms the role gap. Contact your Admin at Admin, then Settings, then Users and Roles. See Why Can't I See Agents, Workflows, or Other Sections in Dave by voolama?
2. 2

   Read the task detail and understand the payload

   The task detail page in Dave by voolama (hellodave.ai) shows the task type, ID, status, metadata, and payload. The payload is the most important element: it contains all the context the workflow passed to the task. Sourced from the tasks help documentation, DEV v0.11.0, confirmed 2026-08-30.

   Do this

   1. At the top of the task detail page, read the task type as the page heading (for example, human_review), the task ID in monospace text, and the status badge. Confirm the status is pending or in_progress. Verify: call GET /api/tasks/{id} in browser developer tools and read the status field.
   2. Read the three metadata cards: Instance (full ID of the parent workflow run), Assignee (your user ID or a dash), and Due (deadline or a dash).
   3. Read the Payload section carefully. The tasks help documentation states: "The Payload section shows the JSON data passed from the workflow to this task. This is the information you need to base your decision on. Review it carefully." Verify: call GET /api/tasks/{id} and inspect the payload field. It is identical to what the Payload section displays.
   4. If the Payload shows an empty object {}, stop. This is a workflow configuration issue. Contact the workflow creator before submitting a decision.
   5. If a Submitted Result section is already present, the task has been completed. Verify: call GET /api/tasks/{id} and confirm the submittedResult field is populated and the status is completed.

   Example

   You open a human_review task. The Payload JSON contains a key draftContent with a 400-word article draft generated by an AI agent. The status badge is amber (pending). You call GET /api/tasks/{id} in browser developer tools and confirm the status field is pending and the payload.draftContent field matches what the UI displays. Decision buttons are visible at the bottom. You read the full draft before deciding.

   Best practice

   • Never submit a decision without reading the full Payload. The tasks help documentation states: "Make sure you understand what you are approving or rejecting before clicking a decision button."
   • To understand the broader workflow context, click the Instance ID in the metadata card to open the parent instance detail page. See How Do I Read a Workflow Instance's Output in Dave by voolama?
3. 3

   Submit your decision: Approve, Reject, or Request Changes

   The decision panel at the bottom of the task detail page in Dave by voolama (hellodave.ai) contains an optional Comment text area and three decision buttons. Your decision determines which outgoing edge the workflow follows from the review node. Sourced from the tasks help documentation, DEV v0.11.0, confirmed 2026-08-30.

   Do this

   1. Scroll to the decision panel. Confirm the three buttons are visible: Approve (green), Reject (red), and Request Changes (outlined). If absent, call GET /api/tasks/{id} and read the status field to confirm the task is still pending or in_progress.
   2. Decide on the appropriate action:
      • Approve if the content meets requirements and the workflow should continue on the current path.
      • Reject if the content is unacceptable and the workflow should not continue.
      • Request Changes if the content needs revision before it can be approved.
   3. Optionally enter a Comment. The tasks help documentation states: "This is especially important for Reject and Request Changes decisions so downstream users or the workflow owner understand your rationale."
   4. Click your chosen decision button. The task status changes to completed and the Submitted Result JSON is recorded.
   5. Verify independently: call GET /api/tasks/{id} in browser developer tools. The submittedResult field contains your decision type, comment text, acting user ID, and timestamp. Also verify in the audit log: navigate to Admin, then Settings, then Audit Log and filter by the task ID. The completion event appears with your user ID and timestamp within seconds, satisfying SOC 2 CC6.1 (AICPA Trust Services Criteria 2017 section CC6.1) and GDPR Article 30.

   Example

   You have read the draft article in the Payload. The second paragraph contains a factual error. You click Request Changes. In the Comment field you write: 'Second paragraph states the wrong year for the product launch. Please correct to 2024 and resubmit.' The task status changes to completed. You call GET /api/tasks/{id}. The submittedResult field shows: {"decision": "request_changes", "comment": "Second paragraph states the wrong year...", "userId": "usr_abc123", "timestamp": "2026-10-13T09:14:22Z"}. You navigate to Admin, then Settings, then Audit Log, filter by the task ID, and confirm the event is recorded with your user ID.

   Best practice

   • Always add a Comment when clicking Reject or Request Changes. The tasks help documentation states: "a brief note explaining why you rejected or requested changes helps workflow owners and other reviewers understand the history." The Comment is recorded in the submittedResult field and appears in the audit log.
   • After submitting, call GET /api/instances/{id} to confirm the instance status has advanced from waiting_review or waiting_user_input to running or completed. See Watch a Run and Read Its Timeline for the instance timeline view.
4. 4

   Troubleshoot common task problems

   Four troubleshooting scenarios are documented in the tasks help documentation, DEV v0.11.0, confirmed 2026-08-30. Each has a specific, independently verifiable fix using the REST API or the Admin UI.

   Do this

   1. No tasks showing in the Task Inbox. The tasks help documentation states: "Set the status filter to All Statuses to see every task. If the list is still empty, confirm that at least one workflow instance is running and has progressed to a node that generates tasks." Verify: call GET /api/tasks in browser developer tools. An empty array confirms no tasks exist for your workspace.

   2. Decision buttons not visible. The tasks help documentation states: "Decision buttons only appear for tasks in pending or in_progress status." Verify: call GET /api/tasks/{id} and read the status field. If it is completed, failed, or cancelled, the API returns a 409 Conflict on any decision submission attempt.

   3. Payload section shows an empty object {}. The tasks help documentation states: "This is a workflow configuration issue, not a task issue. Contact the workflow creator and ask them to verify that the node's payload is configured correctly in the Workflow Editor." Verify: call GET /api/tasks/{id} and inspect the payload field.

   4. "Failed to submit decision" error. The tasks help documentation states: "Refresh the page to get the latest task status. If the task is still pending or in progress, try submitting again. If the error persists, check that the parent instance has not been cancelled or completed independently." Verify: call GET /api/instances/{id} and read the status field. A cancelled instance cannot accept task submissions.

   5. Task Inbox not visible in the sidebar. The tasks help documentation states: "The Task Inbox is available to users with the Admin or Use role." Verify: call GET /api/tasks with the user's session token. A 403 response with the missing permission named (tasks:read) confirms the role gap. Dave by voolama has six default roles: Admin, Create, Curate, Use, Reporting, and Financial. Roles are editable. See Why Can't I See Agents, Workflows, or Other Sections in Dave by voolama?

   Example

   A reviewer reports the Task Inbox is empty. You ask them to set the status filter to All Statuses. Still empty. You call GET /api/tasks with their session token in browser developer tools. The response is an empty array. You navigate to Instances: Running Instances is zero. No workflow instances are running, so no tasks exist. You launch a test instance and ask the reviewer to refresh. You call GET /api/tasks again. The task now appears in the response array.

   Best practice

   • For persistent 'Failed to submit decision' errors, call GET /api/instances/{id} first. A cancelled instance returns a status of cancelled: the task submission returns a 409 Conflict regardless of the task's own status badge.
   • For missing sidebar links, call GET /api/tasks and read the 403 response body. The missing permission string (tasks:read) is named directly. See Why Can't I See Agents, Workflows, or Other Sections in Dave by voolama? for the full role-to-sidebar mapping.