> ## Documentation Index
> Fetch the complete documentation index at: https://docs.marketer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# History and notifications

> Reopen prior conversations, follow notification receipts to their source, and reconstruct what happened across a workspace.

Marketer keeps conversation context, execution history, alerts, and unresolved decisions in separate records. Use each for the question it is designed to answer:

* **Chats and tasks**, filtered to **Chats:** what your team asked, attached, and decided.
* **Activity:** what work ran and what state it reached.
* **Notifications:** what update, alert, or receipt Marketer sent.
* **Awaiting action:** what still needs a human decision.
* Product surfaces: what exists now.

## Use Recents for a quick return

Home shows a short **Recents** list in the sidebar alongside current work and workspace sections.

Select a recent row when you recognize the conversation and want to continue it. Use **Open chats and tasks** in the Recents header, then select **Chats**, when the needed thread is older, archived, or not obvious from its shortened title.

## Reopen a conversation from chat history

Open **Chats and tasks** from Recents or Quick actions, then select **Chats**. Each row can show:

* The thread title
* An **Archived** label when the thread is archived
* Who started it, when that information is available
* The time of its most recent activity

Select the row to reopen the complete conversation.

### Reconstruct the decision

Read the thread in this order:

1. Find the first turn that defined the deliverable.
2. Inspect the campaigns, briefs, creatives, products, or files attached to that turn.
3. Identify later messages that changed the scope, dates, authority, or acceptance criteria.
4. Open any task proposal and note whether it was canceled, edited, or started.
5. Open the final task result or output link.
6. Confirm the current state in the product surface that owns the result.

Continue the same thread only when the new request depends on those established records and decisions. Restate any time-sensitive scope before continuing.

Start a new conversation when the objective, connected account, authority boundary, or source-of-truth record has changed enough that old context could mislead the result.

## Read Notifications as receipts

Open **Notifications** from Quick actions. The page title is **Notifications** with the description **Agent receipts, alerts, and approvals across this workspace.** Items are grouped under **Performance**, **Account health**, **Approvals**, **Agent activity**, **Budget**, and **Billing & team** when those types are present.

A notification row can contain:

* A severity indicator
* A title and short body
* The time it was created
* An unread marker
* A link to the source record when the notification has a destination

Select a linked row to open its conversation, task, approval, workflow, or product record. A row without a link is a static receipt; use its title and time to find the related record in **Activity** or the owning product surface.

### Manage the feed

* Select **Mark visible as read** to mark the notifications currently loaded on the page as read.
* Select **Load older** when more history is available.
* Select **Retry** when the page says it could not load the feed.
* Use unread state to track whether you have seen a receipt—not whether the underlying work is complete.

Reading a notification does not approve a proposal, resolve a waiting task, or confirm a connected-account change.

## Follow an update to its source

Use the same sequence for an alert, completion receipt, or approval notice:

<Steps>
  <Step title="Read the notification type and time">
    Determine whether the row describes an alert, agent receipt, approval event, or budget-related update. Compare its time with the decision window you care about.
  </Step>

  <Step title="Open the linked record">
    Follow the row when it is clickable. If it is not, search **Activity** by the relevant name or return to the product surface named in the notification.
  </Step>

  <Step title="Inspect the full state">
    Read the task steps, result, proposal diff, workflow run, or product record. Do not make a decision from the notification body alone.
  </Step>

  <Step title="Resolve the next action">
    Answer a waiting question in chat, decide a proposal in **Awaiting action**, or open the output in its owning surface.
  </Step>

  <Step title="Verify the current object">
    Confirm the present campaign, creative, brief, workflow, or provider state. A historical receipt remains valid history even after the object changes again.
  </Step>
</Steps>

## Choose the correct record

| Question                                         | Start in                            | Then verify in                               |
| ------------------------------------------------ | ----------------------------------- | -------------------------------------------- |
| What did we ask and which context did we attach? | **Chats and tasks**, then **Chats** | The reopened conversation                    |
| Is the task still working, waiting, or finished? | **Activity** or the task card       | The selected run detail                      |
| Which specialist produced this output?           | **Agents**                          | The specialist detail and output link        |
| Why did I receive this alert or receipt?         | **Notifications**                   | The linked task, workflow, or product record |
| What still needs my decision?                    | **Awaiting action**                 | The proposal or paused-run detail            |
| Did a campaign value actually change?            | The task or approval receipt        | **Campaigns** and, when needed, the provider |
| Where is the generated creative?                 | The completed run                   | **Studio** or **Assets**                     |
| Did a recurring workflow execute?                | The notification or **Activity**    | **Workflow** run history and its output      |

## Distinguish similar-looking events

### Response ready versus task completed

A direct chat response can be ready while a longer task is still running. Open the task card and use its lifecycle state as the execution record.

### Task completed versus action applied

A task can complete by producing an analysis, artifact, or proposal. Confirm a live change separately in **Awaiting action**, the owning product surface, and the provider when appropriate.

### Notification read versus decision resolved

Marking a notification read changes the feed receipt only. A pending approval remains in **Awaiting action** until an authorized person decides it.

### Archived versus deleted

An archived conversation remains visible in **Chats and tasks** under **Chats** with an **Archived** label and can still be reviewed. Treat it as historical context; restate current facts before continuing old work.

## Complete a handoff from history

When another workspace member needs to continue prior work, send them to one thread or task rather than a collection of screenshots. In the latest message, summarize:

1. The current objective.
2. The source records and dates in scope.
3. What Marketer completed.
4. What remains waiting or unverified.
5. The next decision and its acceptance criteria.

They can then inspect the original attachments, proposal, task steps, and output without rebuilding the context from memory.

## Troubleshooting

<AccordionGroup>
  <Accordion title="A recent conversation is missing">
    Confirm the active workspace, then open **Chats and tasks**, select **Chats**, and look for an **Archived** row. A thread created in another workspace will not appear in the current workspace's history.
  </Accordion>

  <Accordion title="A notification does not explain the outcome">
    Open its link, or use its title and time to locate the related run in **Activity**. Read the underlying task or product record before drawing a conclusion.
  </Accordion>

  <Accordion title="The notification is read but the approval remains">
    Read state and decision state are separate. Open **Awaiting action** and use the approval controls on the pending item.
  </Accordion>

  <Accordion title="An old result no longer matches the product">
    Compare the result completion time with current source freshness and later activity. Preserve it as history, then rerun the analysis with an explicit current period when needed.
  </Accordion>

  <Accordion title="The feed has too many low-value receipts">
    Review workspace notification settings and recurring workflows. Keep the notifications tied to decisions your team will review, and use Activity for broad execution history.
  </Accordion>
</AccordionGroup>

## Next step

<CardGroup cols={2}>
  <Card title="Chats and tasks" icon="messages" href="/working-with-marketer/chats-and-tasks">
    Open the hidden combined history route and choose the correct chat or task row.
  </Card>

  <Card title="Navigation and Quick actions" icon="compass" href="/working-with-marketer/navigation-and-quick-actions">
    Reach Notifications, Activity, Awaiting action, and other workspace destinations.
  </Card>

  <Card title="Inspect task history" icon="list-check" href="/working-with-marketer/tasks-and-activity">
    Read the run state, steps, outputs, and Activity record behind a receipt.
  </Card>

  <Card title="Resolve pending work" icon="inbox" href="/working-with-marketer/awaiting-action">
    Move from an approval notice to the exact recorded decision.
  </Card>

  <Card title="Rebuild the request context" icon="messages" href="/working-with-marketer/chat-and-context">
    Continue the thread with the same records, window, and authority boundary.
  </Card>

  <Card title="Monitor recurring work" icon="repeat" href="/product-guides/workflows">
    Use workflow configuration and run history as the execution source of truth.
  </Card>
</CardGroup>


## Related topics

- [Navigation and Quick actions](/working-with-marketer/navigation-and-quick-actions.md)
- [Tasks and activity](/working-with-marketer/tasks-and-activity.md)
- [Chats and tasks](/working-with-marketer/chats-and-tasks.md)
- [Notifications and billing](/workspace-admin/notifications-and-billing.md)
- [Awaiting action](/working-with-marketer/awaiting-action.md)