Skip to main content
A task tracks work that continues beyond one response. Its detail tells you what is happening now, which step or specialist owns the work, what output was produced, and whether a human decision is still required. Do not use elapsed time or a quiet chat as the status. Use the state and latest step shown on the task.

​
Open the same task from anywhere

You can reach a task from several starting points:
  • Select its card in the conversation that started it.
  • Select its row under Currently Running on Home.
  • Open Activity from Quick actions to find active or historical work.
  • Open Agents from the right edge of a conversation, then select the run.
  • Follow a task or run link from Notifications.
These entry points should lead back to the same work. Confirm the task title, workspace, originating conversation, and created time before acting on it.

​
Read live progress

Marketer conversation showing Working for 18 seconds, searched source chips, a completed step, a current step, and a pending step

A running request exposes its searched sources and current step instead of making you infer progress from silence.

The in-conversation activity disclosure has three levels of information: For a longer task, its result block can also show the current step count and a progress control. For coordinated work, open Agents to see the specialist or pipeline behind each step.

​
Follow a running task

1

Confirm the task identity

Match the task to the originating conversation and intended workspace. If two runs have similar titles, use the created time and attached context to distinguish them.
2

Read the current lifecycle state

Use the displayed state—Queued, Working, Waiting, Completed, Partially completed, Failed, or Canceled—as the task’s current truth.
3

Open the current step

Identify the latest active or unresolved step. If an agent owns it, select that agent in the workbench to inspect its goal, progress, and available sources.
4

Resolve a pause once

When the task is Waiting, answer the requested question or decide the linked approval. Return to the same run after the decision; do not start a replacement task while it is resuming.
5

Open the output

At a terminal state, open the result or artifact itself. Compare it with the original request and follow any output link to the product surface that owns it.

​
Respond to each lifecycle state

​
Waiting on a question

Return to the originating conversation and answer with the missing fact or constraint. Keep the reply narrow so it resolves the pause without changing the task’s objective.

​
Waiting on a decision

Open Awaiting action and review the exact proposal. An approval can release the current run or allow a recorded change; a rejection can stop that branch. Return to the task afterward and confirm its new state.

​
Failed or partially completed

Do not immediately resubmit the entire request. First determine:
  1. Which step last completed successfully.
  2. Whether an output was preserved.
  3. Whether the failure came from a disconnected source, missing permission, invalid destination, or the task itself.
  4. Whether retrying would create duplicate creative, workflow, or campaign work.
Retry only after the cause is resolved. If usable output exists, continue from that output instead of repeating finished work.

​
Review a completed task

Completed Marketer launch campaign plan showing three checked steps, the finished result summary, and suggested next actions

Completion is visible at the task and step level; the result still needs a content review.

The completed example shows three distinct layers:
  1. The response explains the outcome in the conversation.
  2. The result block shows 3/3 steps and marks each step complete.
  3. Suggested follow-ups offer separate next requests, such as writing copy or adapting the launch.
Review those layers in order. A suggested follow-up is not work that already happened. For the output itself, verify:
  • It answers the original objective and preserves the stated boundary.
  • Required records, products, or connected sources are the intended ones.
  • Decision-driving figures identify their dates and measurement context.
  • Missing data, failed steps, and assumptions are visible.
  • Generated creative or copy matches approved product facts and review criteria.
  • Any recommended account change is still a proposal unless a separate result confirms otherwise.

​
Use Activity for the workspace-wide record

Open Activity when you do not know which conversation owns the work or when you need history across the workspace. The page separates three views:
  • Agents lists recent agent work and lets you open a selected run.
  • Recent shows workspace activity from the last 24 hours.
  • Full history supports broader history, filters, dates, search, and paging.
Select a run to open its detail. Native agent detail can expose the live run body and an Outputs section. Other activity entries show the recorded event or pipeline detail. Use the open-detail control from the Agents panel when you want a reload-safe full-page record.

​
Activity is an audit trail, not the final object

Activity can prove that Marketer recorded a run or event. It does not replace the current campaign, creative, brief, workflow, or provider state.

​
Avoid duplicate work

Before starting a second task with the same objective:
  1. Check Currently Running on Home.
  2. Search Activity for the task title or agent.
  3. Check Awaiting action for a paused approval.
  4. Open the original conversation for a waiting question.
  5. Confirm that the first run reached a terminal state.
Starting again while the first run is queued, working, or resuming can create overlapping analysis or duplicate artifacts.

​
Next step

Inspect the Agents panel

Move from the task summary to the specialist, output, and source behind a step.

Resolve a waiting decision

Review the recorded scope before approving or rejecting.

Review notifications and history

Follow receipts back to the conversation, task, or product record that explains them.

Verify the final result

Apply a source, time, scope, calculation, and action check.
Last modified on August 9, 2026

Related topics

CampaignsRun your first taskHistory and notificationsChat and contextSlack