---
id: "fluxos.automacoes-execucoes"
titulo: "Run now and read the history"
resumo: "Trigger an immediate run and follow the real result of each execution in the history."
idioma: "en"
tipo: "guia"
categoria: "quadro"
aplicavelDesde: "0.0.16"
capabilities: ["automations.run", "automations.runs"]
estadoEditorial: "aprovado"
nivelEvidencia: "artefato-distribuido"
refFonte: "27574c339b58316408f6be2d62169d59041d07bf"
revisaoFonte: "2026-09-24"
revisor: "mantenedor (v1, 2026-10-03)"
rota: "/docs/en/fluxos/automacoes-execucoes/"
fonte: "pt-br/fluxos/automacoes-execucoes.md"
caminhoPublico: "docs/publica/en/fluxos/automacoes-execucoes.md"
hashFonte: "sha256:78c688865e1980f09fd197b20e85243b02e35867fe60266efa0a5907fdba0bed"
hashDestaPagina: "sha256:8afe13d30710a815920ecd6b187c878985639d1fe26117ec9a1884cf35c16d62"
traducaoAssistidaPorIA: true
traducaoDesatualizada: false
corpoRetido: false
---
<!-- traducao-assistida-por-ia: idioma=EN fonte=pt-br/fluxos/automacoes-execucoes.md fonteHash=sha256:78c688865e1980f09fd197b20e85243b02e35867fe60266efa0a5907fdba0bed estado=atual -->

## Run now

The **Run Now** button, in the routine's detail, queues an immediate execution.

**The return is immediate and is not the result.** It confirms that the run entered the queue — the status
that appears at that instant is the **initial** one, not the final one. The work is still going to happen.

To know the outcome, the path is the history: follow the execution and read the **status** and the **error**
of the first item.

When the button is unavailable, it says why — a paused routine or an operation in progress, for example.

## Execution history

The **Run history** section of the detail, and the executions tab of the screen, show each run:

| Column | What it says |
|---|---|
| **Run** | The run's identification |
| **Workspace** | Where that execution happened |
| **Spend** | The associated cost |
| **Tokens** | The token consumption |
| **Status** | The outcome: completed, failed, unknown |

Without a filter, the history is general. With the filter by automation, only its runs.

## How to use this in practice

1. **After creating a routine, run it once now.** Before waiting for the schedule, a manual execution shows
   whether the request is clear and whether the environment responds.
2. **Read the status, not the "queued".** The queueing message says the run started, not that it succeeded.
3. **Read the error when it fails.** The history keeps the reason; without reading it, the routine looks like
   it just "does nothing".
4. **Check the consumption.** Accumulated tokens and cost are the way to notice a routine that is running
   more than it should.
5. **A skipped run is a result.** When the precheck fails, the execution is recorded as skipped — that is the
   routine working as expected, not an error.

## Scope and limits

- **The initial status is not the outcome.** Treating the immediate response as the result is the mistake
  this page exists to prevent.
- **There may be pagination or an internal limit** in the history. Do not treat the list as the complete
  record of every run to date.

## See also

- [Scheduled automations](/docs/en/fluxos/automacoes/)
- [Creating an automation](/docs/en/fluxos/automacoes-criar/)