Best practice
Troubleshooting
Stages panel displays in red
Part of pipeline goes red
This is usually due to missing columns. A column may no longer be present in an input file, may have been removed from Map Column Headers or may have been renamed by another process.
Columns could also be missing because the dataset they come from is no longer available to the pipeline (for example, unshared or archived). Check the reference dataset inputs and any error message shown within the affected stage.
Joins not picking up a reference dataset
If a reference dataset in a Join was not present when the pipeline was opened, open the Join stage to refresh it or re-add the datasets.
Whole pipeline goes red
Causes can include the above, or a missing dataset used by Automap Values anywhere in the pipeline. This can appear on Trace and is often resolved by opening the Automap configuration. Check whether the reference dataset has been archived, and whether duplicate reference datasets with the same name exist or are not shared.
Missing reference dataset shown in inputs tab but not in stage inputs
Archived/missing reference datasets are not listed in the stage inputs. To remove one, first unarchive it, remove it from the stage inputs, then archive it again.
Outputs
Output not appearing, missing rows, or missing columns
Check the following:
- Inputs: Verify the stage has the correct inputs.
- Outputs toggled on: Ensure the desired output dataset(s) are enabled.
- Mappings/aggregations: Check Map Column Headers and any Aggregate configuration.
- Remove Rows: Review Remove Rows logic to ensure it isn’t removing all rows inadvertently.
In Aggregate, columns still highlighted in the left hand panel will not pass through the operation.
Map Column Headers
Column order not carried through
If columns are reordered in the master schema, the new order is not remembered until:
- A column is deleted from the master schema, or
- A column is renamed in the master schema.
Workarounds:
- Perform any reordering before renaming or deleting columns, or
- Add a second Map Column Headers directly afterwards (no config required) to lock in the order. Downstream Map operations that depend on a specific order may need re-adding.
Joins
Join failing completely or on certain rows
Join keys may not match due to whitespace/case differences. Turn on join point cleansing in the Join, or use a Text Cleanse operation before it.
Row count is increasing unexpectedly
Duplicates on the right-hand side create a one-to-many join, returning multiple combinations. Ensure there are no duplicate join keys in the right dataset.
With transactional data, duplicates may be unavoidable. Consider using an Aggregate to compress the left dataset to the correct grain, producing a one-to-one join.
Calculations
Column name red when referenced or values not appearing in outputs
Check upstream Map Column Headers and Aggregate stages to ensure the column is mapped/included. Stages highlighted in red indicate a Trace error; resolve the error to expose column names. Also confirm the operation is turned on.
‘NaN’ result
‘NaN’ indicates a non-numeric interaction (e.g. text used in a numeric expression) or a divide-by-zero. Use validations to identify non-numeric fields (e.g. ISNUMBER(<value>)).
Pipeline won’t run, Run failed or Technical Error
- Run failed: Invalid data (e.g. operations on invalid dates) or invalid configuration. Review run events for details.
- Technical error: Platform error or connectivity issue. If it persists, contact support@quantemplate.com.
Unexpected UI behaviour
- Refresh the page.
- Clear the browser cache and refresh.
- Ensure Chrome is up to date.
- Disable browser extensions and retry.
Think you’ve found a bug?
Email support@quantemplate.com with as much detail as possible:
- Is this new? When did it start?
- Do others see the same issue?
- Can you reproduce it consistently?
- What exact steps reproduce it?
These details help us reproduce and resolve issues. If it’s blocking progress, we’ll try to suggest a temporary workaround while we work on a fix.
Still stuck?
If you can’t resolve your issue, please email support@quantemplate.com with what you’re trying to do and how the actual output differs from what you expect. If you share a pipeline with us, remember to share dependent datasets from the Data repo as well.