Troubleshooting

Sustainable Catalyst Workbench: Troubleshooting and Recovery

Diagnose and recover common Sustainable Catalyst Workbench failures without losing state.

ProductSustainable Catalyst WorkbenchVerified version5.0.0ComponentCalculation Notes, Chalkboard Translator, Domain Calculators, Embedded Calculators, Engineering Mode, Export Studio, Graph Studio, Hardware and Simulation Handoffs, Parameter Sliders, Prototyping Runners, Symbolic Math, Unit-Aware CalculationUpdatedJuly 17, 2026Reading time18 minutes
← Back to product guides

Sustainable Catalyst Workbench · Troubleshooting

Unit-aware calculation, symbolic math, graphing, engineering notes, domain calculators, exports, and prototyping.

Audience: product users, administrators, reviewers, and integrators.

Last verified version: 5.0.0

Reading time: 18–30 minutes

Status: Published support documentation.

Purpose

This guide uses an evidence-first diagnostic sequence for Sustainable Catalyst Workbench. Preserve state before changing configuration. Determine whether the failure comes from input data, permissions, version identity, browser assets, backend health, schema compatibility, external dependencies, or a product defect.

Prerequisites

  • Exact error message and time
  • Product, backend, package, and schema versions
  • Affected route, feature, record ID, and user role
  • A safe backup or export
  • The synthetic sample for a reference test

Sample data

This article uses a fictional Resilient Community Retrofit Program. The files contain one demonstration row for every documented feature, so each capability can be tested without private or production data.

Download CSV feature examples · Download JSON workspace example

Preview

# Feature Sample action Expected result Classification
1 Chalkboard Translator translate a plain-language energy question into variables, equations, units, and assumptions a reviewable equation and variable table synthetic-demo
2 Symbolic Math differentiate P(t)=120+8t-0.2t² and simplify the result a symbolic derivative with an equivalent-form check synthetic-demo
3 Unit-Aware Calculation convert 450 MWh to kWh and GJ 450,000 kWh and about 1,620 GJ synthetic-demo
4 Graph Studio plot monthly baseline and retrofit electricity use a labeled chart tied to the source rows synthetic-demo
5 Engineering Mode estimate simple payback with stated capital cost and tariff an engineering-style note with cautions synthetic-demo

The downloadable files include all 12 feature rows.

Procedure

  1. Stop repeated imports, submissions, migrations, or destructive retries.
  2. Record URL, feature, action, role, versions, browser/runtime, and expected result.
  3. Run the same feature row in a new synthetic workspace.
  4. If the sample fails, inspect health, logs, browser console, network response, and validation details.
  5. If the sample succeeds, compare real input schema, units, permissions, size, source, and status with the sample.
  6. Check version and schema identity before clearing caches or reinstalling.
  7. Apply the smallest reversible change.
  8. Repeat the sample and real workflow, then document the result.

Common problems

Symptom Likely cause Safe response
Unit mismatch incompatible dimensions were combined correct units or reformulate the equation
Blank graph selected fields are nonnumeric or missing select numeric fields and document missingness
Unexpected result sign, scale, formula, or unit is wrong inspect the equation and run a known reference case
Export blocked validation warnings remain unresolved resolve or document warnings before export

Escalation package

  • Product and version
  • Feature and component
  • Exact error text
  • Reproduction steps using synthetic data
  • Expected and actual result
  • Redacted log excerpt without secrets or personal data
  • Whether a clean sample reproduces the problem

Expected output

  • A reproducible diagnosis or bounded unresolved issue
  • Preserved user and system state
  • A documented workaround when available
  • A support-ready issue summary without private data

Verification

  • The synthetic feature succeeds after the fix.
  • The original workflow succeeds or remains safely isolated.
  • Version and health identity are consistent.
  • No duplicates, stale locks, or unintended cache artifacts remain.
  • The resolution is reflected in a support article, known issue, or release record when appropriate.

Responsible use

Outputs support analysis and learning; consequential engineering or safety decisions require validated data, applicable standards, and qualified review.

Never place credentials, API keys, private URLs, personal records, client documents, or confidential logs in a public article or issue.

Scroll to Top