Once a pipeline is created, you can either edit it to make changes or duplicate it to create a new pipeline based on an existing one. These are two separate features, and each serves a different purpose.

Editing Pipelines

Editing a pipeline is straightforward. You might update details such as the pipeline’s name, adjust its polling rate, or enable additional execution behaviors.

How to Edit a Pipeline

  1. Go to the Pipelines page.
  2. Click the pipeline you want to edit.
  3. Select Edit Settings from the menu (three vertical dots).
  4. Make your changes and save.

Common use cases for editing:

  • Changing the polling rate to run more or less frequently.
  • Renaming the pipeline for clarity.
  • Fixing or updating credentials (e.g., rotating an API key).
  • Enabling recovery or backfill behavior such as Nightly Resync.
  • Adjusting Pipeline Health conditions for errors or stale data.

Pipeline State

A pipeline’s Pipeline State contains the running conditions it remembers between executions, such as its last captured reading and established destinations in the target platform. Most users can view or clear this state from the Advanced tab in the pipeline’s settings.

Clearing state resets the existing pipeline to fresh running conditions and should only be used for advanced troubleshooting. See Pipeline State before clearing it.

Health Monitoring

The Health Monitoring card controls when a pipeline is flagged Errored or Stale.

Setting Configuration
Flag Errored Select 1, 2, 3, 5, or 10 consecutive failed executions, or disable the condition.
Flag Stale Select a duration from 1 hour through 1 week without a successful execution, or disable the condition.
Pause Stale Timer on Weekends Exclude weekend time using the organization’s configured timezone.

See Pipeline Health for condition details, defaults, evaluation timing, and status behavior.

Nightly Resync

Nightly Resync is an optional safety net for supported pipelines whose source devices may upload readings late. It runs an additional execution at midnight UTC and requests the previous 24 hours of data without changing the regular polling schedule.

See Nightly Resync for availability requirements, an example of delayed device data, and instructions for enabling the feature.

Duplicating Pipelines

Duplicating a pipeline creates a new one that copies the configuration and Pipeline State of the original, including its source and target integrations, last captured reading, and established target destinations. This allows the duplicate to continue using the same sensors in the target system.

The duplicated pipeline is identical to the original but starts with no execution history. You can then adjust its settings, such as giving it a new name or assigning a different polling rate.

Common use cases for duplicating:

  • Creating a second pipeline with the same source and target but a different polling interval (e.g., hourly sync plus daily monitoring).
  • Setting up a backup or alternative schedule for pipelines connected to instruments with intermittent connectivity.
  • Preserving existing sensor mappings when creating a new pipeline to the same target system.

Step-by-Step

  1. Navigate to the Pipeline: Go to the Pipelines page and click on the pipeline you wish to manage.
  2. Choose an Action:
    • Select Edit Settings to modify the pipeline in place.
    • Select Duplicate to clone it into a new pipeline.
  3. Configure Settings:
    • Adjust polling frequency, Nightly Resync, or other options as needed.
  4. Save Your Changes:
    • For Edit, changes apply immediately to the existing pipeline.
    • For Duplicate, provide a unique name and save. The new pipeline begins fresh, with up to seven days of backtrack.