Skip to main content

Troubleshooting Template Rendering Errors

Template rendering errors occur when a Node's template or configuration cannot be processed correctly during deployment. These errors often appear alongside SQL compilation issues or missing object references. This guide covers common causes and resolution strategies.

Understanding the Error​

To diagnose template rendering errors:

  • Go to the Deploy tab and open the failed deployment.
  • Double-click on the error to view the full error message and SQL.
  • Look for recurring error types such as Template rendering error, SQL compilation error, or Object does not exist.

Common Template Rendering Errors​

  • Missing or Invalid Parameters

    • Verify that all required parameters are defined in the Node configuration.
    • Confirm parameter values are formatted correctly. For example, wrap string parameters in quotes.
    • Ensure custom Node Types are installed from Packages.

  • Node Type Issues

    • If you changed a Node Type, create a new Node instead of converting an existing one.
    • Confirm that Node Type packages are installed and up to date.
    • Check for missing or invalid Node Type definitions.

SQL Compilation Errors​

  • Object Dependencies

    • Ensure upstream objects exist before deploying dependent objects.
    • Confirm referenced tables, views, and schemas are accessible.
    • Verify object names match exactly, as they are case-sensitive.

  • Column and Schema Issues

    • Confirm all referenced columns exist in source tables.
    • Check for typos in column or table names.
    • Escape special characters in column descriptions when necessary.

Storage and Environment Issues​

  • Storage Location Mappings

    • Verify storage locations are mapped correctly in the target environment.
    • Confirm database and schema mappings point to existing objects.
    • Ensure the deployment user has the required permissions.

  • Authentication Issues

    • Re-authenticate your connection if you encounter OAuth or credential errors.
    • Confirm service account permissions for automated deployments.
    • If network policies are enabled, ensure IP addresses are whitelisted.

Resolution Strategies​

  • Incremental Troubleshooting

    • Deploy a smaller subset of changes first.
    • Break large commits into smaller, testable pieces.
    • Deploy a single Node at a time to isolate the issue.

  • Environment-Specific Solutions

    • Use a clean test environment to isolate problems.
    • Select Clear target environment if errors persist.
    • Drop and recreate problematic objects manually if needed.

  • Recovery Options

    • Redeploy after fixing the underlying issue.
    • Use Retry from failure to continue from the last failed step.
    • Roll back to a previous successful deployment if necessary.

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.