IMSURGE provides a clear, lightweight way to understand whether a pipeline is functioning correctly. Each pipeline’s status is determined by examining the results of its last five executions. This gives you a quick snapshot of recent performance without requiring deep investigation into logs or execution history.

How Pipeline Status Is Determined

Each new execution result is evaluated and classified based on its outcome. IMSURGE then looks at the five most recent executions and assigns one of the following statuses:

Healthy

A pipeline is considered Healthy when at least one of the last five executions has completed successfully.

This indicates:

  • The pipeline is running as expected
  • No persistent or ongoing failure pattern is present

Even if some executions fail intermittently, a recent successful run keeps the status Healthy.

Errored

A status of Errored means all of the last five executions failed due to an error.

Common causes include:

  • Invalid or expired credentials
  • Misconfigured integration settings
  • Connectivity failures
  • Errors in upstream or downstream systems

This status signals that the pipeline is consistently failing and requires attention.

Stale

A pipeline is marked Stale when all of the last five executions returned no data.

Typical reasons include:

  • The data source is not producing new measurements
  • The sensor or device is offline or inactive
  • The selected query range is too narrow to yield results
  • The external system has not published new values

A Stale status highlights that the pipeline is running successfully but isn’t receiving usable data.

Why This Matters

Pipeline statuses give you a quick way to:

  • Monitor operational health at a glance
  • Identify pipelines that need attention
  • Detect upstream data outages before they cause downstream issues
  • Ensure your data workflows remain reliable and timely

Statuses update automatically as new executions occur, so you always have an up-to-date view of each pipeline’s condition.