Modeler answer desk
Help and troubleshooting
Start by checking the active project, model and scenario; then read the specific plan, scope, lint or job message. Modeler fails closed when context or permission is missing so an accidental action does not look like a successful study.
Fast answers
Common Modeler problems
Why is the Run button disabled?+
Activate a model and scenario first. If a model is active, open Run options and check that at least one scenario is selected and no launch is already pending.
Why can I see Data Shop cards but not ingest them?+
The live Data Shop is Enterprise-gated. Locked preview cards remain visible so teams can inspect the catalogue before upgrading.
Why is Attach to current model unavailable?+
Select a compatible active model. Some datasets are new-model-only and some, including IEX-derived bands, are attach-only.
What does Inputs changed since last run mean?+
A component or table edit is newer than the active scenario’s last completed solve. Rerun before presenting the old result as current for those inputs.
Why did the Agent ask me to identify the asset?+
More than one component matched the partial name, or nothing was selected. Choose the asset in Map/Tables or give its exact name.
Where do completed studies go?+
Jobs tracks execution, result chips reopen persisted result IDs, and workflow pages show the latest compatible saved workflow result for the active model and scenario.
Glossary
Terms that prevent expensive misunderstandings
- Project
- A study folder that groups related networks.
- Model / network
- The buses, lines, generators, loads, storage and time series being studied.
- Scenario
- A copy-on-write layer of explicit changes against the model base.
- Result ID
- The persisted identity of one completed solve or workflow result.
- Snapshot stride
- The interval between optimized snapshots; stride 1 preserves native hourly resolution in the current examples.
- Lineage
- The disclosed path and transformation class from source data to materialized input.
- Truth label
- The scope claim attached to a result, such as modeled:nodal-economic-dispatch.
When contacting support
Send evidence, never credentials
- □ Page URL and time of failure
- □ Project, model and scenario names
- □ Dataset/scope or workflow inputs
- □ Job or result ID
- □ Exact visible error text
- □ Screenshot with emails and secrets removed
Never send API keys, database URLs, organisation secrets, signed object URLs or restricted raw market rows.