Problems Pane v2

The designer's Problems pane lists validation warnings and errors for the current design. It combines checks performed in the browser with diagnostics returned by the platform compiler.

Open Problems

Open a Workflow in Design, then click Problems in the resizable designer console at the bottom of the screen.

The pane shows two badges:

The red badge is the current error count.
The secondary badge is the current warning count.

When the designer console is collapsed, its summary shows the first error. If there are no errors, it shows the first warning. Click the summary or Problems to expand the diagnostic list.

Read a diagnostic

Each row begins with an error or warning icon and its message. It can also show:

Code identifies the diagnostic category.
Path identifies the affected Workflow, Step, Property, or YAML line.
Expected describes the required data shape when available.

Long values are shortened in the row. Point to the message or field to see its complete value.

Problem rows do not currently navigate to or select the affected canvas field. Use Path to locate it in the canvas or code view. For YAML syntax errors, use the reported line location in code view.

Search and filter

The console search control matches text in the diagnostic message, code, path, and expected shape.

It has two modes:

Search mode keeps all rows visible and highlights matching rows.
Filter mode shows only matching rows.

Clear the search to restore the complete list. If a filter has no matches, the Problems pane displays No matching results.

When the list updates

The designer validates and compiles a changed Workflow after a short idle period. Diagnostics can therefore update shortly after you stop typing or editing the canvas.

The list also updates when you:

Switch from code to canvas and the Console validates the YAML.
Run the current design.
Save and receive validation or publish diagnostics.
Change a Property, Step, Connection, trigger, or other compiled contract.

When no current errors or warnings remain, the Problems pane displays No problems found.

Errors and warnings

Errors block the operation that reported them. YAML and schema errors also prevent the Console from safely synchronizing invalid code into the canvas.

Warnings remain visible for review but do not necessarily block compilation or saving. The Console omits compiler-originated warnings whose code begins with CS; Workflow-specific warnings remain visible.

Saving and publishing are separate. A save can record a revision even when its publish fails, in which case the Console warns that the Workflow was saved but not published and directs you to Problems.