Pipeline Health provides an at-a-glance diagnostic status for each pipeline. Health rules are configurable per pipeline and can detect repeated execution failures or a lack of recent successful executions.

You can configure health rules while creating a pipeline or later from the pipeline’s Settings tab under Health Monitoring.

Health Monitoring Options

IMSURGE evaluates two independent conditions:

  • Errored: The pipeline has reached its configured number of consecutive failed executions.
  • Stale: The pipeline has gone longer than its configured duration without a successful execution.

Either condition can be disabled. New pipelines default to:

Setting Available options New pipeline default
Flag Errored Disabled; after 1, 2, 3, 5, or 10 consecutive failed executions After 3 consecutive failed executions
Flag Stale Disabled; after 1, 3, 6, or 12 hours; 1, 2, or 3 days; or 1 week without a successful execution After 1 day without a successful execution
Pause Stale Timer on Weekends On or off Off

Healthy

A pipeline is Healthy when neither configured condition is active. A successful complete execution clears an active error streak and restarts the stale timer.

Pipelines with both health rules disabled are identified as Monitoring off in account-level summaries.

Errored

A pipeline is marked Errored after it reaches its configured number of consecutive failed executions.

Errored and interrupted executions count as failures. An aborted execution does not count as an error and breaks the consecutive-error streak. A successful complete execution also breaks the streak.

Common causes include:

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

Stale

A pipeline is marked Stale when it has not completed successfully within its configured duration.

The timer begins from the last successful complete execution. For a newly monitored pipeline with no successful execution yet, it begins when stale monitoring is enabled.

Pausing the Stale Timer on Weekends

Enable Pause Stale Timer on Weekends when weekend time should not count toward the stale duration.

Weekend boundaries are calculated using the organization’s timezone. For example, Saturday begins at midnight in the configured organization timezone, not necessarily at midnight UTC. An Org Admin can change this under Organization Settings. See Organization Timezone.

When Health Is Evaluated

Pipeline health is evaluated:

  • Immediately after an execution reaches a final result, including a manually started execution
  • Approximately once per minute to detect time-based staleness

The Pipeline Health card on the pipeline page refreshes automatically. It displays:

  • Current health status
  • Last complete success
  • Current consecutive-error count and threshold
  • Stale deadline or active stale duration
  • Last evaluation time

Simultaneous Conditions

A pipeline can be both errored and stale internally. Because repeated execution failures usually explain why successful data processing stopped, Errored is treated as the primary status in pipeline lists and account summaries. The pipeline’s detail page retains the stale diagnostic information.

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