You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/2025.3/Guides/user-guides/user-interfaces/gateway/dev/flow-editor/bottom-panel/executions-grid.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,11 +15,11 @@ The Executions Grid displays information about all the [flows][What is a Flow?]
The Executions Grid is automatically displayed when in Debug Mode and a flow is executing or paused from executing; however, it may be manually opened, or closed any time by clicking the Open/Close handle or resized by dragging the handle left or right..
18
+
The Executions Grid is automatically displayed when in Debug Mode and a flow is executing or paused from executing; however, it may be manually opened, or closed any time by clicking the Open/Close handle or resized by dragging the handle up or down.
19
19
20
20
Flows that are Running or Paused are shown with a green background; flows that have raised an [exception][What is an Exception?] are shown with a red background.
21
21
22
-
An execution may be selected by clicking on its entry in the Executions Grid and can be controlled by a set of icons on the top right of the Executions Grid. Selected executions are indicated with a darker background and the actions available are dependent on the state of the selected execution; greyed-out action icons not applicable to the selected executions’ state.
22
+
An execution may be selected by clicking on its row in the Executions Grid and can be controlled by a set of icons on the top right of the Executions Grid. Selected executions are indicated with a darker background and the actions available are dependent on the state of the selected execution; greyed-out action icons not applicable to the selected executions’ state.
Copy file name to clipboardExpand all lines: content/en/docs/2025.3/Guides/user-guides/user-interfaces/gateway/dev/flow-editor/bottom-panel/messages-grid.md
+51Lines changed: 51 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,3 +4,54 @@ linkTitle: "Messages Grid"
4
4
description: "TODO"
5
5
weight: 40
6
6
---
7
+
8
+
# {{% param title %}}
9
+
10
+
## Summary
11
+
12
+
The Messages Grid lists any [issues][What is a Message?] preventing a [flow][What is a Flow?] from being debugged.
The Messages Grid is automatically displayed if there are any issues when attempting to debug a flow; however, it may be manually opened, or closed any time by clicking the Open/Close handle or resized by dragging the handle up or down.
19
+
20
+
Each error message identifies the location of the error, a summary of the error, and a detailed explanation.
21
+
22
+
## Actions
23
+
24
+
### Navigate to Property with Error
25
+
26
+
To locate the error in the flow, double-click on the error. This will automatically navigate to, and select, the [block][What is a Block?] containing the error. The [Property Editor][] will be opened and the [property][What is a Block Property?] containing the error will be selected.
27
+
28
+
See the [Messages Grid][Messages Grid tutorial] tutorial for a step-by-step guide.
29
+
30
+
## Remarks
31
+
32
+
### Known Limitations
33
+
34
+
* The parser is only run when flows are executed. If the flow is not debugged in the Flow Editor before the flow is packaged and published, when an attempt is made to execute the published flow, the parser on the application node will run the parser and any errors raised will result in the flow execution failing and an error message returned in the REST response.
0 commit comments