Skip to main content

From trial to sending recommendations

A workflow's recommendations go through three stages: a trial records each one and sends nothing, then the workflow shows them in your mission control system (MCS) as advice, then it holds each one until a person approves it and it is sent as an instruction. Your plan decides which stages a run can reach, and a policy step in the workflow chooses between the last two.

Where recommendations come from​

Two steps suggest a change on a pass or link: swap (in rain-fade-swap), a backup pass to book before the cancel deadline with the GB it gains in the low case, and lock_loss (in RFI watch), a reroute. The recommendation rides on the item as its action, with a deadline where it has one. See the node reference.

What a run does with them​

Each run records its mode as act_mode:

act_modeWhenRecommendations
shadowA trial: the account is on a 30-day trial of Operator or Operator + Act, or a test run on a plan with ActRecorded on the run's own items, marked mode: shadow, and sent nowhere. Outputs send the forecast without them
offThe plan has no Act: Explore or OperatorThe same, marked mode: off
liveOperator + Act or above, on a run that deliversSent as the workflow's policy says, below

In the Platform, a trial's recommendation shows as Trial, and one on a plan without Act as Not sent. On a plan without Act the builder's Decide stage shows each recommendation as advice, with Send for approval off until Operator + Act. Trial, in an automation's details on Automations, counts what the newest run recorded and the GB it would have gained in the low case.

Show them: suggest​

With no policy step, or one in suggest mode, a live run sends each recommendation with its item to every output, as advice. The connectors show it as a proposal for an operator to act on in the MCS, never as a scheduled change. Nothing waits on a decision, and the Platform shows it as Advice.

Send them for approval: approve​

Add a policy step in approve mode after the step that suggests, so that every path to every output passes through it. For rain-fade-swap, put it between the at_risk condition and the outputs:

{ "id": "approve", "kind": "transform", "ref": "policy", "params": { "mode": "approve" } }

Wire at_risk (its true exit) to approve, and approve to predictions and feed, then save the graph with PUT /predictions/workflows/{slug}. In the builder, the Decide stage makes the same change: choose Send for approval for each recommendation. The full change is in Recipes.

A live run then holds each recommendation. Every output sends the item without it, marked action_status: pending, until someone decides:

  • Send to MCS (approve) publishes the run's mission control outputs again with the recommendation on its item, as an instruction for the MCS to carry out. A swap can cancel a booked pass, so it cannot be undone. The Platform shows it as Followed.
  • Decline (reject) publishes nothing, and the recommendation cannot be decided again.
  • A decision belongs to the workflow, so the next run's same recommendation on the same pass carries it.
  • A recommendation can be decided until its deadline (a swap's is the provider's cancel deadline, otherwise the pass's start, or for a link the end of its span), and only on the workflow's newest run that delivered.
  • Approval reaches the MCS through mission control outputs only. A destination keeps the item as it was first sent, pending.

Decide on Passes by opening the pass (Deciding one), over MCP, or with /predictions/actions. On Passes your sign-in holds the act:approve scope, so no key is needed. Over MCP or the API, use a live key with it: Approve actions from your own tools on Integrations ticks it.

Plans and refusals​

You ask forNeedsRefused with
A run that deliversOperator403 plan_required, plan: standard, feature: run
Sending a recommendation (approve)Operator + Act403 plan_required, plan: pro, feature: act, even for one held while the account had it
Declining oneThe act:approve scope, on any plan403 insufficient_scope without it
A late or stale decisionThe newest run, before the deadline409 action_expired, 409 action_stale, or 409 action_decided

Do not retry a 403 plan_required: the answer stays the same until the plan changes. See Errors and limits.

Auto-eligible delivery, sending a recommendation into the MCS without a person approving it, is not available yet.

Next: hold rain-fade-swap's swaps for approval with the recipe.