Skip to main content

No Stages Rendered

No Stages Rendered

Description​

The "No Stages Rendered" error typically indicates there is an incorrect or missing configuration within a Node that is preventing the template from rendering properly.

Possible Causes​

  • Dimension Nodes - The "Business Key" may not be configured in the Node Configuration. You need to select the business key columns and move them to the selected side using the arrow button.
  • View Nodes - The "Override Create SQL" option has been enabled, but the SQL in the Create SQL tab is incorrect, missing elements, or doesn't include a proper "CREATE OR REPLACE VIEW" statement. Validate that your SQL statement would execute correctly if pasted directly in your data platform.
  • Node Type Switching Issues - When you switch a Node from one type to another, the old metadata may still be present, causing rendering issues. The solution is to create a new Node from scratch rather than switching types.
  • Missing Required Configuration - Check for any required fields marked with red asterisks in the Node configuration. All required fields must be properly configured for the template to render.

Possible Solutions​

  • Check Node Configuration - Look for any missing required fields (marked with red asterisks) in the Node properties.

  • Validate SQL - If using custom SQL, ensure it's syntactically correct and would run in your data platform.

  • Review Template Errors - Click the arrow at the bottom of the Node to expand error details.

    Screenshot of Coalesce showing a DIM_DATE_NODE configuration with various date-related columns and their transformations, and a results panel below indicating successful validation, creation, and data loading steps.

  • Recreate Problem Nodes - If switching Node types, delete and recreate the Node rather than converting it.

  • Check Dependencies - Ensure all referenced objects exist and are properly configured The error essentially means the Jinja template cannot generate the necessary SQL stages due to missing or incorrect configuration parameters.

Next Steps​

If errors continue after troubleshooting, create a support ticket. Include the full error message, deployment ID, and steps to reproduce the issue to help the support team investigate.