---
title: "Block Execution"
slug: "v20-block-execution"
updated: 2026-11-01T19:57:24Z
published: 2026-11-01T19:57:24Z
canonical: "docs.telosalliance.com/v20-block-execution"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Block Execution

## Overview

Block Execution pauses parts of Pathfinder Core PRO while it keeps running. You can stop everything, stop one subsystem such as all scenes, or stop a single scene, router, panel or logic flow folder, while leaving the rest working.

Use it during maintenance windows, when testing a new configuration, while troubleshooting, or when making many changes at once without them triggering each other.

## How It Works

### The Three States

Every component that can be blocked has one of three states:

| State | What it does |
| --- | --- |
| **Inherit** | Follows its parent. If the parent is blocked, this is blocked; otherwise it runs. |
| **Block** | Stops execution here and in everything below that inherits. |
| **Override** | Runs even when a parent is blocked. Use it for exceptions such as maintenance tools. |

Everything starts as **Inherit**, which at the top level means "not blocked".

### What Can Be Blocked

Blocking works down Pathfinder's object tree. Block a manager and everything under it is blocked unless it is set to Override.

| Manager | Object path | Children that can be blocked |
| --- | --- | --- |
| Logic Flows | `LogicFlows#0` | Logic flow folders |
| Property Groups | `PropertyGroups#0` | Property groups |
| Routers | `Routers#0` | Individual routers |
| Scenes | `Scenes#0` | Individual scenes |
| Timers | `TimeEvents#0` | Timers, date/time and day-of-week events |
| User Panels | `UserPanels#0` | Panels and their pages |

### What Stops and What Keeps Working

| Component | When blocked | Still works |
| --- | --- | --- |
| Scenes | Triggers are ignored, whether manual, scheduled or automated. | Viewing and editing scenes. |
| Routers | Route change requests are rejected. | Querying routes, editing router configuration, source and destination metadata. |
| Property Groups | Property synchronization stops. | Property values are still monitored; the group can be edited. |
| User Panels | Button presses do not trigger logic flows, hardware mappings send nothing, and panel changes do not reach the objects they control. | The panel still renders and shows state; it can be edited. |
| Timers | Timers, date/time and day-of-week events do not fire. Skipped events are logged. | Countdowns keep running; timers can be viewed and edited. |
| Logic Flows | Translators do not process input changes and combiners do not evaluate. | Inputs are still monitored; flows and folders can be viewed and edited. |

## Blocking and Unblocking

Open **System > Configuration** and click **View** next to **Block Execution**.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-block-execution-button.png?sv=2026-02-06&spr=https&st=2026-11-02T12%3A19%3A17Z&se=2026-11-02T13%3A19%3A17Z&sr=c&sp=r&sig=cSJfpI%2BwQuqWvkmMrcA3ueRdRO3Il42P2pWFF8PU334%3D)

The Block Execution dialog lists each manager with its current state highlighted. Click **Inherit**, **Block** or **Override** to change it; the change takes effect immediately.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-block-execution-list.png?sv=2026-02-06&spr=https&st=2026-11-02T12%3A19%3A17Z&se=2026-11-02T13%3A19%3A17Z&sr=c&sp=r&sig=cSJfpI%2BwQuqWvkmMrcA3ueRdRO3Il42P2pWFF8PU334%3D)

Click **+** next to a manager to show the components under it and set them individually. Here the OnAir logic flow folder is blocked while the rest of Logic Flows runs:

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-block-execution-expanded.png?sv=2026-02-06&spr=https&st=2026-11-02T12%3A19%3A17Z&se=2026-11-02T13%3A19%3A17Z&sr=c&sp=r&sig=cSJfpI%2BwQuqWvkmMrcA3ueRdRO3Il42P2pWFF8PU334%3D)

A blocked logic flow folder's name is shown in red in the Logic Flows **Views** tree.

To unblock, set the component back to **Inherit**.

### From the API or a Logic Flow

`BlockExecution` is an ordinary property, so it can also be set over the SapV2 API (port 9600) or as a logic flow End Point, for example from a scene or a panel button:

```plaintext
set Scenes#0 BlockExecution=Block
set Scenes#0.Scene#system_restore BlockExecution=OverrideBlock
set Scenes#0 BlockExecution=Inherit
get Scenes#0 BlockExecution
```

Over the API, the Override state is written `OverrideBlock`.

## Example: Maintenance Window with Exceptions

You need to freeze all automation for maintenance, but a maintenance panel and two maintenance scenes must keep working.

1. **Set the exceptions first.** Set the maintenance panel and the two maintenance scenes to **Override**. Doing this before blocking their parents avoids a moment where they are blocked too.
2. **Block the managers.** Set Scenes, Routers, Property Groups and User Panels to **Block**. Everything except the three exceptions stops.
3. **Do the maintenance.** Blocked scenes, route changes and property syncs are skipped and logged. The maintenance tools work normally.
4. **Unblock in a controlled order.** Set each manager back to **Inherit** one at a time, checking each before moving on: Property Groups first so synchronization is healthy, then Routers, then User Panels, then Scenes.
5. **Remove the overrides** if you no longer need them, by setting them back to **Inherit**.

Other common uses:

- **Test a new scene without side effects:** block `Scenes#0` and set the new scene to Override. It runs, but any scenes it would trigger are blocked.
- **Edit many scenes at once:** block `Scenes#0` so no half-edited scene fires, then unblock when you are done.
- **Replace router hardware:** block just that router so no route changes are sent to it during the swap; other routers keep working.

## Things to Know

> [!WARNING]
> Block Execution is not saved. After Pathfinder Core PRO restarts, everything returns to Inherit (unblocked). This is deliberate: a forgotten block that survived a restart could leave automation stopped. Re-apply any blocks you still need after a restart.

- **Nothing is queued.** Operations that are blocked are skipped, not delayed. When you unblock, nothing is replayed; the system carries on from that point.
- **Configuration is not affected.** You can still add, edit and delete scenes, flows and other components while they are blocked. When unblocked, they run with the new configuration.
- **Each cluster node has its own block state.**
- **Block at the highest level that does the job.** One block on `Scenes#0` is easier to track, and to undo, than a hundred blocks on individual scenes.
- **Keep track of what you have blocked.** Note it in your maintenance ticket or runbook, and plan when it will be unblocked.