Messages
Every error, warning and note a check, a run or a refused action can show, grouped by what you change to clear it. In the Execution Report, each message links to its page here.
About a node¶
A node's own check of its settings or of the data reaching it. Each node's page lists the messages it can show.
- Aggregate column not in input
- Aggregated column not numeric
- Column headers repeated
- Column without a header
- Concatenated columns differ
- Constraint applied
- Constraint left members out
- Constraint matches nothing
- Constraint not met
- Constraint parameter unknown
- Constraint rule settings unusable
- Constraint type unknown
- Cost falls as quantity grows
- Cost steps incomplete or overlapping
- Date not readable
- Day and month order unclear
- Decimal mark unclear
- Demand history rows unreadable
- Field matches several columns
- File format not supported
- Filter column not in input
- Filtered column not numeric
- Join column not in input
- Join inputs share no key
- Join key without both columns
- Location types don’t match scenario
- Model difficulty profiled
- Model loosened to solve
- Model unsolvable even when loosened
- Network numbers too far apart
- Number outside its allowed bound
- Objective needs emissions data
- Optimization evidence
- Planning window dates unusable
- Precision target met
- Required field absent
- Row doesn’t fit its table
- Row left out
- Rules cannot all be met
- Script changed nothing
- Sheets not read
- Some join keys unmatched
- Text padded with spaces
- Value not a plain number
- Yes/no value not readable
About the scenario¶
How the tables of a scenario fit together. They are checked when Create Scenario assembles the scenario and again when an analysis reads it, so the fix is usually in the data or the Map node that made one of the tables.
- Carrying cost period missing or unknown
- Column mixes value types
- Component can’t reach plant
- Computed value not finite
- Coordinate outside the world
- Currency not stated
- Demand left unserved
- Emissions unit unclear
- Filter cannot be read
- Filter matches no product
- Flow rows repeated
- Lane capacity too small
- Lane minimum not met
- Location missing from Locations
- Location not on any lane
- Location values conflict
- Location without coordinates
- Mapped table empty
- Network shortfall totals
- Optimized plan unit differs
- Policy price absent
- Product missing from Products
- Product named ALL
- Production capacity too small
- Quantities in unconverted units
- Quantity below zero
- Quantity without a unit
- Recipe makes several products
- Recipe missing from Bill of Materials
- Recipe product unknown
- Recipe units disagree
- Recipe uses its own product
- Required value blank
- Row stated twice
- Rows match no scenario table
- Scenario file unreadable
- Scenario table absent
- Scenario upload incomplete
- Source and target identical
- Supply capacity exceeded
- Supply has no use
- Table names differ only in case
- Tags cannot be read
- Two lanes set one connection
- Unit conversion missing
- Unit conversions unusable
- Unit not stated
- Value breaks a table rule
Checks before a run¶
Validate and Run check the canvas first, for every node: inputs connected, required settings filled in, each connection carrying the kind of data its port takes. A workflow with one of these errors does not start.
- Connection end does not exist
- Connections form a loop
- Create Scenario node absent
- Id names several nodes or connections
- Input connected more than once
- Input receives wrong data
- Inputs not readable from code
- Newer version saved elsewhere
- Node id, type or position absent
- Node setting not recognised
- Node type not available
- Required input not connected
- Required setting empty
- Selected input unavailable
- Setting value unusable
- Step description missing
- Step name missing
- Time budget above the limit
- Workflow deleted
- Workflow without nodes
Run limits and failures¶
The run itself: its time and storage limits, cancellation, and failures that are not about your data.
- Cancellation requested
- Data source name taken during run
- Data source unreachable
- Disk space limit reached
- Further messages hidden
- Inputs changed while run queued
- Memory limit reached
- Node message unreadable
- Product updated while run queued
- Run already ended
- Run computer stopped responding
- Run environment removal unconfirmed
- Run environment unavailable
- Saving interrupted
- Saving took too long
- Storage limit reached
- Time limit reached
- Unexpected failure
Refused actions¶
An action taken in the app, or by an agent for you, was refused before it changed anything: a delete, an upload, or a request the action does not take. The message names what stands in the way.