Respond to a waiting workflow

A run can wait for a decision before writing through a connector, or for information an agent needs to continue. Open the run detail to see which response is required. A waiting run has not finished, even if earlier nodes succeeded.

Find the waiting run

Open the automation and its execution logs, then select the run marked Waiting. Check the version and run input so you know which execution you are reviewing.

An operation approval names a connector action and shows its proposed input. An agent question instead asks for an answer, with choices or a text field. These are separate interactions: answering a question does not approve a later write.

Approve or reject a write

Read the operation and The step would call with carefully. Check the recipient or destination, the content, and any identifier that selects what will change.

Choose Approve to allow the operation. The run resumes and attempts the write; check the node result and effects afterwards. Choose Reject if the request is wrong or should not happen. Rejection prevents that operation and fails the run.

The card keeps telling you where the run stands when something goes wrong. If the approval cannot be loaded, the card says so and offers Try again; the run keeps waiting until someone decides. If your choice was not recorded, the card says so and keeps Approve and Reject available, so you can choose again. If someone else decided first, the card shows the decision on record.

A live run checks that the connector has a usable credential before it asks for approval: when none is configured, the node fails with that reason instead of waiting for a decision.

You cannot revise parameters on the approval card. Reject an incorrect request, fix the workflow or run input, and test the correction before starting a new live run. Changes to the approval policy do not release an already pending card. See Approval concepts for the decision lifecycle and approval policy configuration for operator rules.

Let one automation write without approval

A write that waits for a person on every run — a morning digest posting to Slack — can be allowed for that one automation. Open the automation's General tab: Runs without approval lists each write to an outside system its latest version makes; a write on Tale's own surface, such as creating a task, never waits by default. An Owner or Admin turns the write on and saves; from then on, its live runs make that write straight away, and its box on the canvas says Runs without approval. Every other automation, and every other write of this one, still asks.

A rule of the approval policy that requires a person for the action still wins over an allowance. Each grant and withdrawal is recorded in the audit log, and deleting the automation removes its allowances. A coding agent connected over MCP reads the same allowances, and the key of an owner or admin can change them.

Answer an agent’s question

When an agent node uses ask_human, the run detail displays The agent needs your answer to continue. If choices are offered, answer the questions on the card. For an open question, enter text under Your answer, then choose Send answer & resume.

Give the missing information directly. If the agent asks which document to use, name the document or provide its identifier rather than a general instruction to continue. The waiting node resumes with your answer, and the run may later need another answer or an operation approval. Owners, Admins, and Developers answer on the run detail. When the run works a task, the question also appears on the task, where anyone who can open the task answers it.

Correct and test the workflow

Changing a workflow definition is separate from responding to its current run. Save a corrected version in the workflow editor, test it against mocks, then deploy it when it is ready for live use. Saving a version does not revise a call already waiting for approval.

A mock test does not perform external connector writes or request their live approvals. For a practical walkthrough, follow Build a workflow with approvals. After a live decision, inspect both the run outcome and the audit log; permission to proceed and successful execution are different results.