Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Calculation errors and warnings reference

Use this reference to identify HASS Cloud calculation errors and warnings by name or number, and apply the recommended action. For a guided troubleshooting workflow, see Resolve calculation errors.

Calculation errors

MissingCalculationName (1022)

  • Type: Validation
  • Location: Calculation tool / Issues panel
  • Cause: Required calculation label was not provided
  • What to do: Enter a valid name and retry

NullCalculationRequest (1020)

  • Type: Request validation
  • Location: Issues panel
  • Cause: Calculation request payload was incomplete
  • What to do: Re-open calculation tool and submit again

MissingDarcyOptions (1030)

  • Type: Method config validation
  • Location: Issues panel
  • Cause: Darcy method selected without required fluid options
  • What to do: Complete Darcy settings before calculating

MissingKFactorDiameterMappings (1031)

  • Type: Method config validation
  • Location: Issues panel
  • Cause: K-factor mapping mode enabled without mappings
  • What to do: Add mappings or disable mapping mode

MissingMinimumFlowPressure (1032)

  • Type: Method config validation
  • Location: Issues panel
  • Cause: End-head/minimum target settings missing
  • What to do: Add target settings and retry

MissingSprinklerDensityAreas (1033)

  • Type: Method config validation
  • Location: Issues panel
  • Cause: Density/area mode missing sprinkler density/area input
  • What to do: Fill sprinkler density/area data

InputValidationErrors (1066)

  • Type: Aggregated validation
  • Location: Issues panel (detailed list)
  • Cause: One or more fields are invalid or missing
  • What to do: Correct highlighted fields, then recalculate

Invalid* value errors (1050–1067)

  • Type: Value/range validation
  • Location: Issues panel + highlighted cells
  • Cause: Input value format/range is invalid (area, density, diameter, pressure, flow, etc.)
  • What to do: Replace with valid engineering input and retry

NoSprinklersInRemoteArea (1070)

  • Type: Business rule
  • Location: Issues panel
  • Cause: Remote area tool could not form a valid area
  • What to do: Review sprinkler setup and remote-area assumptions

InvalidEndHeadConditions (1071)

  • Type: Business rule
  • Location: Issues panel
  • Cause: End-head setup is not valid for the current model
  • What to do: Adjust calculation mode or end-head setup

NoPipeTableBookAssigned (1072)

  • Type: Configuration
  • Location: Issues panel
  • Cause: Pipe table source is missing
  • What to do: Assign/select a valid pipe table book/page

MaxNodesExceeded (1073) / MaxPipesExceeded (1074) / MaxSourcesExceeded (1075)

  • Type: Capacity limit
  • Location: Issues panel
  • Cause: Model exceeds supported limits
  • What to do: Reduce model size or split into smaller sections

Pipe/Fitting lookup errors (1101–1123)

  • Type: Data mapping / library lookup
  • Location: Issues panel
  • Cause: Required pipe/fitting/diameter mapping data not found
  • What to do: Verify pipe tables, fittings, page assignments, and library integrity

Darcy initialization errors (1201–1208)

  • Type: Method data validation
  • Location: Issues panel
  • Cause: Required Darcy fluid/temperature/viscosity inputs missing or incompatible
  • What to do: Complete Darcy fluid-property inputs

NoSourceFoundInSystem (1301)

  • Type: Topology / model completeness
  • Location: Issues panel
  • Cause: No water source in SDF
  • What to do: Add/repair source definition

PipeNotFoundForPump (1302) / SprinklerNodeNotFound (1303) / SourceNodeNotFound (1304) / HoseStreamNodeNotFound (1305)

  • Type: Topology reference error
  • Location: Issues panel
  • Cause: Component references missing node/pipe
  • What to do: Repair connectivity references

MultipleComponentsConnectedToNode (1306)

  • Type: Topology rule
  • Location: Issues panel
  • Cause: Node has conflicting component attachments
  • What to do: Separate or reassign components

NoDemandPointsFoundInSystem (1307)

  • Type: Model completeness
  • Location: Issues panel
  • Cause: No active demand points detected
  • What to do: Add/enable demand points

Source relationship errors (1308–1310)

  • Type: Source validation
  • Location: Issues panel
  • Cause: Static/residual source values are inconsistent
  • What to do: Correct source pressure/flow relationships

InvalidKFactorRange (1311)

  • Type: Validation
  • Location: Issues panel
  • Cause: K-factor input is invalid for use case
  • What to do: Correct sprinkler/source K-factor usage

SystemNotConnected (1312)

  • Type: Connectivity
  • Location: Issues panel (group highlighting)
  • Cause: Network has disconnected islands
  • What to do: Connect all required sections to supply path

InsufficientSystemPressure (1313)

  • Type: Hydraulic feasibility
  • Location: Issues panel
  • Cause: Available supply cannot satisfy model demand
  • What to do: Increase supply or reduce losses/demand

MultipleSourcesNotAllowed (1314)

  • Type: Rule validation
  • Location: Issues panel
  • Cause: Current calc mode does not allow multi-source setup
  • What to do: Use compatible calc mode or simplify sources

ConvergenceFailure (1316)

  • Type: Solver
  • Location: Issues panel
  • Cause: Solver cannot converge to a stable hydraulic solution
  • What to do: Simplify/adjust model inputs; review pump/supply sizing

NoCandidateAreasSuccessfullyTested (1400)

  • Type: Remote area analysis
  • Location: Issues panel
  • Cause: Candidate areas failed feasibility checks
  • What to do: Review remote area assumptions and model data

NegativePressure (2000)

  • Type: Calculation failure
  • Location: Issues panel (detailed diagnostics)
  • Cause: One or more nodes fall into non-physical pressure conditions
  • What to do: Follow probable-cause guidance; fix direction/supply/loss issues

RestrictiveFlow (2001)

  • Type: Calculation failure
  • Location: Issues panel
  • Cause: System requires unrealistic/restricted flow behavior
  • What to do: Check directionality, elevation, and restrictive segments

InlineDirectionConflict (2002)

  • Type: Direction conflict
  • Location: Issues panel (actionable detail)
  • Cause: Inline directional components oppose each other
  • What to do: Flip/reorient directional components consistently

InternalError (9998) / UnknownError (9999)

  • Type: System error
  • Location: Issues panel / toast
  • Cause: Unexpected backend/system failure
  • What to do: Retry; if persistent, capture bug report

Calculation warnings

InsufficientSupplyPressure (1000)

  • Type: Warning
  • Location: Results warnings + Issues context
  • Cause: Supply had to be boosted to complete solve
  • What to do: Review source assumptions and demand

LargeKFactorValue (1001)

  • Type: Warning
  • Location: Results warnings
  • Cause: Unusually large sprinkler K-factor input
  • What to do: Confirm data entry

PipeLengthTooShortForNodeSpacing (1002)

  • Type: Warning
  • Location: Results warnings / geometry context
  • Cause: Pipe length is shorter than geometric span
  • What to do: Increase length or adjust node geometry

SourceBelowMinimumPressure (1003)

  • Type: Warning
  • Location: Results warnings
  • Cause: Source is below configured minimum pressure
  • What to do: Review source settings/supply

SprinklerBelowMinimumPressure (1004)

  • Type: Warning
  • Location: Results warnings
  • Cause: Sprinkler below minimum operating pressure threshold
  • What to do: Review demand, sizing, and supply

InlineComponentsAutoCorrected (2000)

  • Type: Auto-correction warning
  • Location: Results warnings
  • Cause: App auto-corrected conflicting inline directions
  • What to do: Review corrected components and save model

ComponentConventionFlipped (2001)

  • Type: Auto-correction warning
  • Location: Results warnings
  • Cause: Global directional convention was reversed to resolve issue
  • What to do: Verify flow direction conventions and results

PumpCurveFlowUndefined

  • Type: Results warning
  • Location: Calculation results header warnings
  • Cause: Determined pump operating point not defined for flow
  • What to do: Adjust pump curve/setup

VariablePumpRpmBelowNfpa20

  • Type: Compliance warning
  • Location: Calculation results header warnings
  • Cause: Variable-speed pump operating too low relative to rating
  • What to do: Review pump setup and operating scenario