_ESP_RunUpdates
Delivers notifications of changes during debugging. The Server sends notifications only when the project is in trace mode.
| Column | Type | Description |
|---|---|---|
| key | string | The type of the update. See table below. |
| value | integer | A number associated with the update, determined by the Key column. |
| stream | string | The name of the stream if the update notifies an event related to an individual stream; otherwise, stream NULL. |
| info | string | Additional information associated with the update. Its format depends on the type of the update. |
Below is the table of the types of updates that the Server sends as debugging commands. The Value and Stream columns in this table correspond to the Value and Stream rows under Column in the _ESP_RunUpdates stream.
| Key | Value | Stream | Description |
|---|---|---|---|
| TRACE | 0 or 1 | None | Enabled (1) or disabled (0). |
| RUN | 0 or 1 | None | Event Stream Processor paused (0) or running (1). |
| STEP | <count> | None | The project was single-stepped, either manually or automatically. The value contains the number of the steps made. No details are provided about the streams that were stepped. |
| BREAK | <bp-id> | <stream-name> | The breakpoint with ID <bp-id> was triggered on stream <stream-name>. These updates may come either before or after the corresponding update "RUN 0". |
| NO BREAK | <bp-id> | <stream-name> | A breakpoint with ID <bp-id> on the stream <stream-name> had its leftToTrigger count decreased, but has not triggered yet. |
| EXCEPTION | None | <stream-name> | An exception occurred on stream <stream-name>. These updates may come either before or after the corresponding update "RUN 0". |
| REQUESTEXIT | None | None | A request to shut down the project received. |
| EXIT | None | None | All the user streams have exited and the project is about to shut down. |