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

# Automation lifecycle

> Understand generation, execution, inspection, saving and reuse.

A generated automation, a completed run and an accepted result are different milestones. Start at Run when using an existing automation; start at Generate when creating or changing one.

<h2 id="generate">
  1\. Generate
</h2>

Describe the intended operation and review the proposed scope. Generated code or a card does not, by itself, show that the model changed. Direct actions in a conversation may execute separately: read the task activity and inspect the application.

<img src="https://mintcdn.com/ideatura/eBNfPtgOkPvBoGUx/images/setup/automation-card.svg?fit=max&auto=format&n=eBNfPtgOkPvBoGUx&q=85&s=b06edf477de770fc4be2796848aa2531" className="w-full h-auto mx-auto" alt="Saved Hello world automation card. The green check indicates compilation; use the run control and inspect the execution report to establish whether it ran." width="1449" height="471" data-path="images/setup/automation-card.svg" />

<h2 id="run">
  2\. Run
</h2>

Confirm the application, document, view, parameters and intended treatment of existing output. Run one small scope. A manual Run action can have different consequences from an agent permission setting; read [Modes and access](/studio-reference/ui-connections).

<h2 id="inspect">
  3\. Inspect
</h2>

Compare the native result with the request. Check counts, references, omissions and unintended changes. A success message establishes neither completeness nor correct geometry. Use [Review and recover](/ai/review).

<h2 id="save">
  4\. Save
</h2>

Save the accepted native document and the automation separately. Use a name that describes the operation and retain a known working version before adapting it. Follow [Save an automation](/automation/automation-basics/name-and-save-an-automation-so-you-can-find-it), then reopen the saved entry to confirm its identity and defaults.

<h2 id="reuse">
  5\. Reuse
</h2>

Test changed inputs on a small scope before a wider run. Decide whether existing output should be skipped, appended, replaced or updated. See [Reuse across projects](/automation/reuse-projects).

<h2 id="share">
  6\. Share
</h2>

Check the destination workspace, audience and editing rights. Confirm whether a colleague receives a copy and verify its parameters from their account. See [Share an automation](/automation/share).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.