The Expiration Date feature allows you to automatically stop pipeline scheduling when a project ends or when instrumentation is removed from the field. This helps prevent unnecessary executions while preserving your pipeline configuration and history.

Overview

Many users know in advance when their projects will end or when they plan to remove their instrumentation. To simplify this process, IMSURGE allows you to set an expiration date on a pipeline.

When a pipeline reaches its expiration date:

  • The scheduler will no longer automatically execute it.
  • The pipeline frequency remains unchanged.
  • The pipeline remains visible in your list of pipelines and can still be viewed as last configured.
  • The pipeline’s frequency will display as “Expired” in the pipeline list.

Behavior After Expiration

Even after a pipeline has expired:

  • You can still manually execute it.
    • Manual executions still count toward tracked usage and any applicable free-tier limits.
    • The pipeline executes using the last known configuration from its most recent scheduled run.
  • When viewing an expired pipeline’s executions, a notice appears at the top of the page indicating that the pipeline has expired.

Resuming Scheduling

If you want an expired pipeline to resume automatic scheduling:

  1. Open the Pipeline Settings page.
  2. Edit the Expiration Date field.
  3. Either remove the expiration date entirely or extend it to a future date.

Once saved, the pipeline will return to its normal scheduled behavior based on its defined frequency.

Example Use Cases

  • Project-based monitoring with a defined completion date.
  • Temporary instrumentation deployments (e.g., short-term construction monitoring).
  • Seasonal data collection that should pause automatically after a fixed period.