Back to Help

Troubleshoot Evaluation Problems

Find why a value, state, geometry result, or artifact row does not match expectation.

TroubleshootingintermediateReference guide

What this is

Troubleshooting means tracing the evaluated path from input -> formula -> state -> geometry -> output.

Most issues come from incorrect inputs, failed evaluation, fallback defaults, or output filtering.

Follow the evaluation pipeline: inputs -> parameters -> variables -> state -> geometry -> nested blocks -> artifacts.

Identify the problem

Start by naming what is wrong. Each problem type points to a different stage.

  • Value is wrong: inspect inputs, parameters, and variables.
  • State is wrong: inspect variables, the selection formula, and fallback state behavior.
  • Geometry is wrong: inspect the active state, injected fields, and directives.
  • Output is wrong or missing: inspect artifact scope, filters, selected fields, raw/resolved mode, and layer visibility.

Debugging workflow

Step 1 - Confirm the input

  • Check instance parameters in the Properties Panel.
  • Confirm you selected the correct instance.
  • Verify the intended values and overrides are present.

Step 2 - Check parameters

  • Compare raw values with resolved parameter values.
  • Look for missing inputs, invalid values, or defaults used unexpectedly.

Step 3 - Check variables

  • Use the Debug tab to inspect variable results.
  • Look for formula errors, circular dependencies, or lookup table misses.

Step 4 - Check state selection

  • Confirm which state is active.
  • Verify the selection formula and fallback behavior.

Step 5 - Check geometry

  • Confirm geometry is coming from the active state.
  • Check injected fields and directives that affect the visible result.

Step 6 - Check nested blocks

  • Use this step only when the block contains child block references.
  • Verify inherited values and nested instance overrides.
  • Confirm nested evaluation matches the parent expectation.

Step 7 - Check outputs

  • Verify artifact scope, filters, selected fields, and raw/resolved mode.
  • Confirm layer visibility if rows are missing.
  • Stop at the first step where the result diverges from expectation.

Where to inspect

  • Properties Panel -> inputs and parameters.
  • Debug tab -> parameters, variables, and active state.
  • Formula editor -> expressions, references, and formula helpers.
  • Outputs -> artifact filtering, projection, scope, and raw/resolved mode.

Common failure patterns

  • Default values used unexpectedly -> missing input or failed parameter resolution.
  • Wrong state selected -> selection formula mismatch or fallback state.
  • Geometry looks wrong -> incorrect state or injected field failure.
  • Nested blocks behave differently -> inherited values or nested overrides.
  • Output rows missing -> filtering, scope, or hidden layers.

Quick checklist

  • Are the inputs correct?
  • Are parameters resolving as expected?
  • Are variables producing expected values?
  • Is the correct state active?
  • Is geometry coming from the correct state?
  • Are nested blocks receiving the right inputs?
  • Are outputs filtered or scoped correctly?

Try it now

  1. Open the Control Power Panel.
  2. Change a parameter.
  3. Trace the change through parameters.
  4. Trace the change through variables.
  5. Confirm the active state.
  6. Compare the geometry result.
  7. Open Outputs -> Data and compare the output result.
  8. Identify where the result first changes from what you expected.

Key idea

Debug the evaluation pipeline, not just the visible result.

Docs

How to trace where evaluation issues occur.

Reference

Exact limits and fallback behavior.