Follow a run

Every time an Application runs, the console keeps a record of it: which device ran it, each step with its status, what the step was given and what it returned. Use it to watch a run as it happens and to find out why one failed.

Open a run

Open Build›Executions and select a run. It also opens from a run alert, and from Open run on the operations map.

The status at the top right says where the run stands:

Run status	Means
Accepted, Planning, Ready	Being prepared. A run a trigger created without starting it waits on Ready until someone selects Start.
Running	Working through its steps, also while it waits for an approval.
Paused	Someone paused it. No further step starts until it is resumed.
Succeeded	Finished. A failure that an On failure or On timeout path handled doesn't make a run fail.
Failed	A step failed and nothing in the graph handled it.
Cancelling, Cancelled	Someone cancelled it, or a more important run took its drone.

The steps run from left to right. Each step carries its own status:

Status	Means
Pending	Not reached yet.
Running	Under way now. The bar under it shows how far it has got, as the device reports it.
Succeeded	Done.
Failed	It didn't work. The run takes the failure path, or ends.

The way the run took is drawn in green, and the line into the step under way moves. Grey dashed lines haven't been taken. The name at the top opens the Application, at the version this run used.

Look inside a step

Select a step. The panel on the right shows what happened in it:

• Input: what the step was given, for example the position the drone flew to.
• Output: what the step returned. Later steps can use it.
• Duration, and the Attempt when a step was retried.
• Auto-selected asset: when the platform had another device run this step, which one and why.
• Warnings, for example a detour around a no-fly zone.

Find out why a run failed

A failed run shows the reason in a red bar across the top. Select the failed step to see its input and the error, in the platform's words.

The error says	What to do
goTo rejected … beyond the … range at …% battery	The target was further than the battery reaches. Charge the drone, or start closer.
A no-fly zone	The way was blocked. See Sites and no-fly zones.
interrupted: manual control took over	Someone flew the drone by hand while the run was using it.
An approval step failed	Someone rejected it, or nobody answered in time. See Ask for approval.

A step that never ran says so: it has no input or output.

Watch it live

While a run is going, select Live View at the top. A small window shows the device's position on a map; select the camera button to add its video. Select the small picture to swap map and video, and drag the corner to make the window bigger.

When you close the window, a video it started stops.

Start, pause or cancel a run

Button	Does
Start	Starts a run that waits on Ready, for example one a trigger created without starting.
Pause	Starts no further step. A step under way finishes.
Resume	Continues from where the run was paused.
Cancel	Ends the run. A drone in the middle of a flight is sent home, not left in the air.

If the device can't stop what it was doing, the run still ends, and the bar at the top says what the device may still be doing.

Hold back an Application

To stop an Application from starting at all, for example while you fix it, select the pause button next to it on Build›Applications. You can pause the whole Application or one of its Skills. Nothing starts it then: no event trigger, schedule, webhook or manual run. Runs already going finish normally. Holding back an Application needs the organization administrator role.

Troubleshooting

• No graph snapshot. The run is still being planned. Wait a moment.
• Pause and Cancel are greyed out. Your account needs the operator role.
• Live View is missing. The run has ended, or it doesn't use a device.
• A step is still running long after the device is done. Check the device under Manage›Operations›Assets; if it is offline, cancel the run.

Next steps