Skip to main content
Some failures cannot be fixed safely by the Maintenance Agent alone, for example a page that asks to accept terms, confirm a change or pick between options with real consequences. With Decision Required, the agent does not guess. It asks a person, the run waits, and the recovery continues from the answer.
Decision Required is enabled per workspace. It needs a connected Slack workspace and a channel the CloudCruise bot has been invited to, also when you answer through the API. Contact CloudCruise to turn it on.

​
How it works

  1. A run hits a blocker that needs a consequential choice.
  2. CloudCruise posts a decision card in your Slack channel with the question, what the run has done so far and the answer options. Webhooks subscribed to agent.decision_requested receive the same question.
  3. The run waits while the card is open.
  4. A person answers, the agent continues the recovery and the run resumes. agent.decision_answered reports how the decision closed.
The first accepted answer wins, wherever it comes from. Later answers and answers from someone who is not allowed to answer are rejected, and that person is told privately.

​
Where you can answer

Without webhooks, read the open question with GET /run/{session_id}/decision/pending or cloudcruise run decision <session_id>.

​
Answer options

​
Add Error Code

The agent usually suggests a code with the question: one of your workspace’s codes, or a new one in your naming, such as PORTAL-E004, with a short description. Add Error Code opens a confirmation where you can rename the code and pick its Behavior, the same choices as in Error Handling > Error Codes; only Stop run and notify changes how a run ends today. Add and stop run stops the run with that code and saves it. Depending on your workspace, the code is either added to the step in a new workflow version right away, so later runs stop with it without asking, or waits for approval in Error Handling > Error Codes. The confirmation says which. Through the API or CLI, add_error_code saves the suggestion as it is. Without a suggestion, it only stops the run.

​
If nobody answers

A card waits 5 minutes by default; a workspace or workflow can set 30 to 600 seconds. When the time runs out, the run stops with its original error and the card says it timed out. The agent never makes the choice on its own. The expired card still offers Answer anyway to save it for next time. A late answer does not resume the run; it is offered the next time the same error happens. See Remembered decisions. If a card cannot be sent, for example when no channel is configured or the run fails outside the active hours of your decision notification rules, the recovery continues without asking. CloudCruise also limits how many cards a recovery, a run and a workspace can open, and does not resend an identical card for a period.

​
Deprecation: input_required

The input_required error-code action is retired. New codes cannot use it, and existing ones were converted to alert. The execution.input_required webhook event and POST /run/{session_id}/new_input_variables were removed; subscribe to agent.decision_requested and answer at its respond_url instead.