Skip to main content

Error: GraphExecutor halted and finished

Error​

If you receive the "GraphExecutor halted and finished; encountered failures for node: [node ID]; no nodes skipped" error when running a Nodes, Subgraph, Job, etc. within a Workspace, this is typically due to the objects you are trying to complete a Run operation on in Coalesce not yet being created in the target location in Snowflake.

The image shows an error message indicating that the `GraphExecutor` process was halted and finished due to encountering failures for a specific node identified by the ID `[5ae2e643-cec7-44df-a3eb-19f10c0e15de]`. The message also notes that no other nodes were skipped during this process. The image shows a failure message in a production environment with a specific `Run ID` of `12324`. The `Run failure reason` indicates that the `GraphExecutor` halted and finished due to encountering failures for nodes `[261, 294]`, and several other nodes `[262, 289, 295, 296, 298, 7f443543-0760-443e-93fb-3eda1cffa94c, b38dd2b1-782b-4bb8-a0d4-4c60d698b13c]` were skipped as a result.

You may also see a message in the results pane that say Table <fully qualified table name> does not exist or not authorized.

Solution​

In your Workspace, first execute the Create operation for the objects you are trying to execute the Run on. Once the Create has completed successfully, you may execute the Run operation. In the Workspace, the Create operation executes the Data Definition Language (DDL) for your objects, while the Run operation executes the Data Manipulation Language (DML) for your objects. These operators are comparable to Deploy (Create) and Refresh (Run) for your Coalesce Environments.