Skip to main content

A run fails with "Remote execution failed"

What it means when a server-side script can't reach your Companion App.

Symptom​

A run in the history of a web trigger, scheduled job or post function, or a scripted field's preview, shows one of these errors:

  • Remote execution failed. Status: followed by the status code the Companion App answered with, and Status text: with its reason
  • Remote execution failed: followed by an error, when the Companion App couldn't be reached or its answer couldn't be read

Find the cause​

  1. Open the Settings tab and look at Current status in Secured Execution.

The Companion App was briefly unavailable​

Cause: The Companion App didn't answer during that run, or answered with an error. Script Master records the failed run and doesn't retry it.

Solution: Test the item again from its editor. For a web trigger, the caller can send the request again. If the error comes back, contact support with the error text and the time of the run.