Understand agent run history

What this explains

• This article explains understand agent run history in the context of AI agents and automation.
• Use it when you need to understand the concept before choosing a workflow or changing setup.
• If you need click-by-click instructions, open one of the related how-to guides after reading the concept.

Key ideas

Idea 1

What it means

Inspect past runs, inputs, outputs, status, and approval state. This concept affects how users choose the right workflow, avoid setup mistakes, and interpret what they see in DitLead.

Idea 2

Where it shows up

Look for this concept inside AI agents and automation and in adjacent workflows that depend on the same data, permissions, accounts, or campaign state.

Idea 3

Why it matters

Understanding this before acting helps prevent duplicate data, bad-fit audiences, disconnected senders, failed campaigns, or confusing handoffs between teammates.

Idea 4

What to check

Before making changes, confirm the workspace, affected records, required permissions, and any downstream workflow that may use the result.

How to use this

• Open the most relevant related guide when you are ready to act on the concept.
• Share the article with teammates if it defines a term or workflow your team uses repeatedly.

FAQ