Skip to content

Approve or decline an automation

PortalCLIBeginner~5 min

A schedule or a webhook starts work on its own, and it runs only after you approve it. You do this in the portal: open your App, open its Automations tab, read a plain summary of what the automation will do, and press Approve or Decline. There is no row id or hash to copy. If you prefer a terminal, the same review is hadron automation, below.

An automation here is a schedule or a webhook of an App. What an automation may do is the server's answer, and who may approve it is the server's call too: being able to see an App does not by itself let you approve its automations. Background on automations is in How multi-node automations work.

Approve an automation in the portal

  1. Open the portal, go to Apps, and open your App.
  2. Open the Automations tab. Each row shows the automation's name, whether it Starts as a Schedule or a Webhook, and its Status: Approved or Waiting for approval.
  3. Open an automation by its name. The page shows a status and a plain summary: When it runs, What it can read, What it writes, Tools it can use, Limits and What it cannot do. A fact the server cannot show reads not stated.
  4. Press Approve. The page says Approved.

The list is only what you may approve. Nothing to review here does not prove the App has no automations: only someone who may approve one sees its row. Manual runs are not listed on this page.

Decline an automation in the portal

Open the automation and press Decline, then confirm.

  • If the automation was approved, declining switches it off: its next run fails until it is approved again. The confirmation says so.
  • If it was not approved, declining only records that you declined it.

When an automation changes

Approval is for the automation as you reviewed it, not for its name.

  • A changed automation must be approved again. If an approved automation is edited, its status reads Changed since it was approved and its next run fails until you approve it again. Do not rely on the list to show the change: open the automation itself.
  • A stale approval is refused. If it changes while you are reading it, your Approve is refused, the page shows the new summary, and nothing is approved. Read the new summary, then approve again.

Approve or decline from the CLI

You will need the hadron CLI for this part: install it and sign in first. The App is --app <ref>, else the active App (hadron app use); pass --app on every command, as below, so none of them acts on a different App you selected earlier. A trigger is named schedule/<name> or webhook/<name>; a bare <name> works when exactly one trigger of the App has it. Nothing is ever picked for you: no match and several matches both refuse.

hadron automation ls --app hrn:app:acme.com:ops
hadron automation approval schedule/nightly --app hrn:app:acme.com:ops
hadron automation approve schedule/nightly --app hrn:app:acme.com:ops
hadron automation decline schedule/nightly --app hrn:app:acme.com:ops
  • ls lists what you may approve, with its state.
  • approval prints the plain summary. --depth adds the graph and the hash.
  • approve shows the summary on stderr first, asks you to confirm, and sends the hash it just showed. --yes skips the prompt, never the display; without it a non-interactive caller is refused and nothing is changed.
  • decline revokes an approval, or records a decline. It never needs the summary, so you can decline an automation you cannot read.

If the automation changed since you looked, approve exits 5 and retries nothing; run hadron automation approval <name> --app <ref> again. An unknown or invisible name exits 4. Answering no at the prompt exits 6. The full flag and exit-code list is in the CLI reference.