Runtime state and controls
The editor toolbar shows the selected Runtime target's state. Verify its name before acting; switching targets shows the new target's own state.
| State | Available actions |
|---|---|
| Stopped | Admin can Build, Start, or Debug; no instance exists and Object calls are rejected |
| Starting | Wait for Init; Admin can Stop if needed |
| Running | Use and accept the App in a runtime Page or Player; Admin can Stop |
| Debugging | Inspect logs, variables, and breakpoints; Continue a pause or Stop |
| Stopping | Wait for cleanup without repeating lifecycle actions |
| Faulted | Inspect the cleanup error and restart Runtime target; start and deployment are blocked |
Target delivery, Start, Debug, and Stop require Runtime target Admin. Runtime Object calls remain subject to App permissions. Design validates local page interaction only, never executes Object / Query calls. Preview calls require Run / Debug; calls in Stopped reject and log errors to Console.
Starting and stopping
Start / Debug uses the delivered version, creates a new instance, and executes Init. Object methods are admitted only in Running / Debugging. Editing saved files does not change the running version.
Stop cancels and drains calls, disposes initialized resources in reverse order, closes Providers, and releases resource claims. Successful cleanup returns to Stopped. The next run initializes new instances; instance memory does not survive Stop, while explicitly persisted data does.
Fault recovery
A business fault preserves its original error and is reported once as a live event. Successful cleanup returns to Stopped without restarting. Record the error and reproduction conditions; Build after source/configuration repairs, then explicitly Start / Debug.
Cleanup failure or its ten-second deadline enters Faulted with a static message, not an endless busy indicator. Resources must not be treated as released. Run / Debug / Deploy remain blocked until Runtime target is restarted through the site recovery procedure.
If Starting does not finish, Stop can cancel initialization. Inspect Console, connections, and resource claims. A debugger pause requires Continue or Stop.
Accepting a new version
Save → verify target → Stop → Build → Start / Debug → accept → Stop
Build first when the target has no deployment for this App. Design values prove only layout and basic interaction. Validate real data, roles, success, faults, and recovery on a runtime Page.