Task Board

The Task Board consolidates chat tasks, Autonomous Work, and other run records from the task perspective. Use it to find and follow work; return to the source chat, Autonomous Work item, or WakerFlow to change configuration.

​

Open the global or Waker Task Board

• Global: left navigation → Task Board for account-wide work.
• Waker: Waker Management → select a Waker → Work → Task Board for that Waker only.

The global Task Board has three working areas: Use list view for precise lookup and update-time comparison. Use lane view to inspect task flow by state. Open a row for details, or use the assignee to verify the responsible Waker or Group. The Waker Task Board narrows the same workflow to one Waker, which is useful for inspecting that role's load, failures, and recent deliverables.

Both views show the task title, assignee, source, state, latest update, and a detail entry point. The global board additionally provides cross-Waker and cross-Group summaries and filters.

​

Find a task

1. Decide whether to search globally or under one Waker.
2. Search by task title, Waker, or Group name.
3. Narrow the list by assignee, trigger method, and task state.
4. Expand the date range when an older task is missing.
5. Confirm the target by title, assignee, source, state, and update time.

An unread count means there is new activity, not that the task completed. When a filtered list is empty, clear filters and confirm that you are not viewing the wrong Waker.

​

Understand states

Completed is not the same as accepted. Verify files, links, external objects, tests, and key conclusions.

​

Open task details

Check:

1. source and trigger time;
2. executing Waker, Group, or WakerFlow;
3. run input, workspace, and permission confirmation;
4. current step, pending action, or first failure;
5. final reply and artifact location.

The board shows a summary. Use the source detail for the complete chat, business log, workflow nodes, and trigger data.

​

Handle pending actions

1. Open the item and return to the source chat or flow.
2. Read the context, request, and impact.
3. Supply missing information or approve/reject the operation.
4. Confirm that execution resumes.
5. Return to the board and verify the updated state.

For a high-risk action, inspect the target, scope, and rollback plan—not only the button label.

​

Use the Approval Workbench

Path: left navigation → Dashboard → Approval Workbench. Task Tracking helps you notice blocked work; the Approval Workbench collects every item that needs an answer, choice, or confirmation. Items can come from Group collaboration, a single-Waker chat, or WakerFlow. Common types include plan confirmation, clarification, plan changes, cancellation confirmation, and workflow questions. Filter by Status, Type, and Source; Source is useful when you only want items from one Waker, Group, or WakerFlow.

1. Filter for Pending, then narrow by the source you are responsible for.
2. Read the item, initiator, source task, and update time so that you do not act on an obsolete request.
3. Select Handle to return to the source chat or workflow, where the complete context and controls are available.
4. Answer, approve, or reject the request and confirm that execution continues as expected.
5. Return to the Approval Workbench, verify that the item is Handled, and check the task's final status in Task Tracking.

Handled means that this human request received a response; it does not mean the entire task completed. If an item has no available source link, use its source name and timestamp to locate the Waker, Group, or WakerFlow. Do not resubmit the same answer just to force a status refresh.

​

Handle failures

Do not retry repeatedly without diagnosis. Check:

1. complete inputs and accessible attachments;
2. workspace, project, and execution device;
3. Waker or WakerFlow availability;
4. model, Skill, connector, and permission;
5. external authorization, rate limits, and network.

Retry from the source after repair so the full context and run record remain visible. Start a new task only when you need a different workspace, executor, or target.

​

Manage history

• Use names such as “project + task + stage/date” for searchability.
• Save required artifacts before deleting records.
• Deleting a task record does not reverse file or external-system changes.
• Prefer filters and naming conventions over deleting audit history for visual cleanliness.

​

Troubleshooting

The Task Board cannot force-edit a task state and does not replace complete business logs or artifact acceptance.