Skip to main content
Awaiting action is the workspace inbox for work that cannot continue without a human decision. It brings together recorded approvals, paused workflow decisions, and links back to proposals that need review. An item here describes a pending decision. It is not evidence that the proposed change already happened.

​
Know which decision you are making

Marketer exposes two distinct review points. The controls and consequences are different. Review the complete item before selecting a button.

​
Review a proposed run in chat

Longer agent work can begin with a step-by-step proposal.
Marketer conversation showing a seven-step Creative Pipeline proposal with Dismiss, Edit, and Approve and Run controls

A task proposal shows its planned work before the longer run starts.

​
Read the proposal

  1. Match the proposal title to the outcome you requested.
  2. Expand Steps and read the full sequence.
  3. Confirm the plan gathers the intended workspace context and evidence.
  4. Check the production or action steps against your authority boundary.
  5. Confirm the final step returns the artifact or result you need.
Then select:
  • Dismiss when the run should not happen.
  • Edit when the objective is right but the plan needs a different scope, input, step, or output.
  • Approve & Run when the plan is correct and you want the listed work to start.
After Approve & Run, the proposal changes into task progress. Follow the task until it is completed, waiting, partial, failed, or canceled. This decision approves the listed run—not every action its result might later recommend.

​
Open the Awaiting action inbox

Open Awaiting action from Quick actions. The page title is Awaiting your action and the description identifies it as pending approvals and proposals that need a human decision. The page can show decidable approval rows above a feed of other pending items. Start with rows that have Approve and Reject controls, then use linked feed items to open their full source context.

​
Decide an agent-proposed change

A connected-account proposal row can show:
  • The affected entity or object name
  • The action or tool that proposed the change
  • Who or what submitted it, plus its age
  • A spend-impact badge when that impact is known
  • The reason for the proposal
  • One or more fields shown as current value → proposed value
  • The relevant ad-account identifier when available
1

Confirm the object

Match the entity name, provider account, and object level to the record you intended to change. Similar names are not enough.
2

Read the diff

Review every current value and proposed value. If the item says it did not record a change summary, open the source tool or conversation and do not approve from the incomplete row.
3

Check impact and evidence

Confirm the size and direction of the change, the reason, the supporting measurement window, and the workspace guardrail that permits it.
4

Choose Approve or Reject

Select Approve only when the recorded object and diff are correct. Select Reject when the scope is wrong, stale, unsafe, or unsupported.
5

Read the confirmation

Approval opens Approve this change? Read the account and spend warning, then select Approve again to record the decision or Cancel to return without deciding.
An approval gives the proposing agent permission to apply that specific change. The change is not complete until Marketer runs it; verify the result in the owning product surface and, when needed, the connected account.

​
Decide a paused workflow run

A workflow approval row identifies a specific scheduled or triggered run that paused. It can show:
  • The requested decision and workflow name
  • A Paused badge
  • The action and number of items that will change
  • A list of affected entities, followed by an additional count when the list is longer
  • When that entity set was picked
  • Whether other runs of the same workflow are also waiting
  • Approve, Reject, and Review the automation controls

​
Review the scope

Select Review the automation when you need to inspect the trigger, steps, or guardrails that created the decision. Return to the pending row and compare the configuration with the scope shown there. If the row says the workflow did not record what it will change, review the automation before approving. Missing scope is not evidence of a zero-impact change.

​
Choose the branch

  • Approve opens Let this automation continue? The dialog restates what the current run will do. Confirming releases that run to continue immediately.
  • Reject stops the current paused run from continuing.
  • Review the automation leaves the decision pending while you inspect its configuration.
When several runs of the same workflow are waiting, the decision applies only to the run shown. The remaining runs stay paused. After you decide, the interface can show a Decision sent receipt while other runs remain unresolved; their own approval rows appear as the workflow progresses.
A recurring workflow can have more than one paused run, each with its own selected entities. Do not assume one approval resolves every pending run for that workflow.

​
Follow a linked pending item

Some items in the lower feed open the conversation, creative review, workflow, or task that owns the decision rather than exposing buttons directly in the inbox.
  1. Open the linked row.
  2. Read the full request, result, and current status.
  3. Make the decision in the owning surface.
  4. Return to Awaiting action and confirm the item is no longer unresolved.
Use the notification’s summary for wayfinding only. The linked record supplies the scope you need for the decision.

​
Verify what happened after the decision

Do not stop at the success message. Follow the chain for the item you decided: If an approved change is still processing, keep the original decision and task open. Do not submit a duplicate proposal.

​
Use a material-change review

Before approving work that can affect spend, targeting, delivery, or customer-facing material, verify:
  1. Workspace and provider: the intended workspace and connected account.
  2. Object: the exact campaign, ad set, ad, workflow, or creative.
  3. Current and proposed state: every visible field in the diff or run scope.
  4. Magnitude: the budget, status, audience, count, or delivery impact.
  5. Evidence: source, date window, attribution context, and freshness.
  6. Guardrail: the applicable business constraint and approval authority.
  7. Result check: where you will confirm the provider or product state afterward.

​
If the decision cannot be completed

Open the proposing conversation or tool. Request the exact object, current value, proposed value, and effect. Reject or leave the item pending until it is independently understandable.
Confirm the workspace, your role, the proposal state, and the connected account. Another authorized member may already have decided it.
Reject it or leave it unresolved, refresh the underlying analysis, and create a new proposal from current provider state.
Approval and application are separate. Check the task or workflow state, then verify provider processing before considering a retry.
Check whether it is a different run of the same automation. Compare the requested time and selected entities; each paused run requires its own decision.

​
Next step

Follow resumed work

Confirm that a task or workflow moved out of Waiting and produced its result.

Verify campaign state

Inspect the exact advertising object after an approved change processes.

Review workflow history

Confirm what a released or rejected workflow run did next.

Trace the original request

Return to the conversation or notification that supplied the decision context.
Last modified on August 9, 2026

Related topics

History and notificationsApprovals, guardrails, and autonomySpecialistsTasks and activityWorkflows