Runtime states and controls

The editor toolbar shows the App state on the current Runtime target. Verify the target name before choosing an action. After switching targets, the state belongs to the newly selected target.

The typical state flow is:

Stopped → Previewing → Stopping → Stopped

Stopped → Starting → Running / Debugging → Stopping → Stopped

State quick reference

State	Meaning	Available action
Stopped	The App has no active runtime instance	Admin can Build, Preview, Start, or Debug
Previewing	The editor is previewing a Page from the current target	Inspect the Page and interactions; Admin uses Stop when finished
Starting	The App is preparing to start	Wait; Admin can Stop when necessary
Running	The App is running normally	Use and accept the App; Admin can Stop when finished
Debugging	The App is running under debug control	Inspect debug information; Continue when paused; Admin can Stop when finished
Stopping	The App is stopping and releasing occupied resources	Wait for Stopped; do not begin another runtime action

Preview, Build, Start, Debug, and Stop require Runtime target Admin. A target User can inspect state and use an App that is already Running, but cannot change runtime state. See Runtime target accounts and permissions for the complete boundary.

Stopped

Stopped is the starting point for delivering a new version, starting normal operation, or entering Debug.

• Build checks the saved project and delivers a new version to the current target.
• Preview checks a Page from the version on the current target inside the editor.
• Start starts the version already delivered to the target.
• Debug starts a delivered Debug version under debug control.

If Preview, Start, or Debug reports Build required, the target does not have a version of this App suitable for that action. Verify saved content and the target before running Build. See Build and runtime acceptance for the complete procedure.

Previewing

Previewing means that the editor is displaying a Page from the version already delivered to the current target.

• Inspect layout, input, navigation, and Page interactions.
• Real Object calls still reach the current target and can cause equipment actions.
• When finished, an Admin uses Stop and waits for Stopped. Build, Start, and Debug become available again after Stopped.

Previewing is not a production-running state and does not include unsaved changes. To update the Page, Stop, save, and Build again.

Starting

Starting means the start request was accepted and the App is acquiring resources and completing startup preparation.

• Wait for Running or Debugging.
• Do not repeatedly select Start, Debug, or Build.
• To cancel startup, an Admin uses Stop and waits for Stopped.

When startup fails, the interface preserves the error and returns to Stopped after cleanup. Record the original error, then inspect licensing, equipment, resources, or App initialization.

Running

Running means the App has entered normal operation.

• Accept Pages, roles, external equipment, and normal business flows in the runtime page or Player.
• A target User can inspect and use an App that is already Running.
• Before delivering a new version, switching to Debug, or ending this run, an Admin uses Stop.

Saving in the editor does not change the version that is Running. To bring a change into runtime, Stop, run Build again, and then Start.

Debugging

Debugging means the App is running under debug control.

• Inspect logs, variables, and breakpoint results.
• When a breakpoint pauses execution, use Continue to resume this debug session.
• When debugging is complete, an Admin uses Stop and waits for Stopped.

Debugging is not a production-running state. For normal site operation, stop debugging, complete the required Build and acceptance, and then Start.

Stopping

Stopping means shutdown has begun and the App is ending work and releasing equipment and other resources.

• Wait for Stopped.
• Do not Preview, Build, Start, Debug, or repeatedly Stop during shutdown.
• After Stopped, begin the next Preview, Build, Start, or Debug operation.

A runtime fault also initiates shutdown cleanup and eventually returns to Stopped. Stopped means cleanup is complete; it does not prove that the fault is fixed.

Common issues

Preview, Start, or Debug is unavailable

Confirm that the current state is Stopped, the current App has been delivered to the selected target, and the target session is Admin. A wrong target, insufficient permission, or missing Build can prevent the action.

Starting or Stopping does not finish

Do not retry actions repeatedly. Preserve the original error and time shown by the interface, then check the target connection, License, external equipment, and occupied resources. Follow the site recovery process when required.

The App returns to Stopped with a runtime error

Preserve the error and reproduction conditions first. Run Build again after repairing source or configuration. If no version change is required, Start only after confirming site conditions. Do not hide a recurring fault by repeatedly starting.

Changes are saved, but the Running App still has old behavior

This is expected. Save updates the project only. An Admin stops the current instance, runs Build again, and then uses Start or Debug.

What a person must confirm

• The toolbar names the Runtime target approved for this task.
• Preview, Start, Debug, or Stop will not cause an unapproved equipment action or outage.
• After a fault returns to Stopped, the root cause and recovery conditions are understood.
• A successful Build and Running state do not replace site process and safety acceptance.

See Runtime lifecycle for state concepts and Runtime and site delivery for the complete delivery path.