Choose a topic, then select a question to reveal its answer. Contact our support team if your question is not covered.

Can IMSURGE create reports, alarms, charts, or thresholds?

No. IMSURGE is the data infrastructure that enables communication between the devices and source platforms that produce data and the target platforms that use it.

IMSURGE moves data between those systems. Reports, alarms, charts, calculations, threshold notifications, and similar features are provided by the target platform.

Do you store collected data?

IMSURGE keeps event data files generated during pipeline executions for 90 days. You can use these files to review or download the data handled during a specific execution.

IMSURGE does not store individual sensor readings in a searchable data repository. You cannot use IMSURGE to search readings across executions, build charts, or maintain a long-term record of sensor data. Those capabilities are provided by the target platform receiving the data.

Can I install IMSURGE on my phone or tablet?

Yes. IMSURGE is a progressive web app that can be added to the Home Screen on Android, iPhone, and iPad without downloading it from an app store.

See Install IMSURGE as an App for Chrome and Safari instructions.

How far back can I fetch data when creating a pipeline?
The available backtrack period depends on the source integration and its API. For a data-pull source, the launch options show the supported backtrack periods when you create a pipeline or start a manual execution.
How do you handle API limits?

API limits vary by vendor:

  • For IP-based limits, we work with vendors to lift restrictions or increase the limits applied to IMSURGE servers.
  • For limits tied to an API key, choose a reasonable polling rate or distribute requests across multiple keys when the vendor supports it.

Check the source’s Integration Library page for any known restrictions.

What's the difference between duplicating a pipeline and creating a new one?

Some pipelines save configuration during their executions. This is particularly important when a target integration creates sensors or maintains mappings to existing sensors.

  • Duplicate a pipeline to preserve its saved configuration and continue using the same target sensors.
  • Create a new pipeline to start with fresh configuration. Depending on the target, this may create duplicate sensors.

See Edit and Duplicate Pipelines for more information.

Why are there gaps in my data, or why are some readings not reaching the target?

Poor cellular signal, power interruptions, or other connectivity issues can delay uploads from a device to its source platform. Some devices upload their newest readings first when they reconnect.

A pipeline may retrieve those recent readings and continue forward before the older readings become available, leaving a gap in the synchronized data.

For supported pipelines, Nightly Resync provides a fallback. It requests the previous 24 hours of source data again at midnight UTC, giving delayed readings another opportunity to reach the target without changing the regular polling schedule.

How do I choose a polling interval?

Start with the recommended polling rate for the source integration. Choose a different rate only when your reporting requirements, the device’s upload frequency, or API limits call for it.

See Polling Rates and the source’s Integration Library page for specific guidance.

What should I do if my pipeline fails?

Open the execution log to see where the pipeline failed and review the error details. See Monitor Executions for help interpreting execution results.

Unexpected errors may be related to the source or target platform. Visit the IMSURGE support page for help if the issue continues.

Why does my pipeline execution keep getting aborted?

An aborted execution usually means that the source had no data available for the requested period. Common causes include:

  • The source has not published a new reading yet.
  • The pipeline polls more frequently than the device reports.
  • The device is offline or experiencing connectivity issues.

Try a polling interval that better matches the device’s reporting frequency. See Polling Rates for guidance.

Can IMSURGE work with platforms that push data instead of providing an API to poll?

Yes. External platforms, devices, and gateways can push data directly to IMSURGE through Ingress Endpoints. Pipelines using these integrations can run when new data arrives instead of polling on a schedule.

Which vendors are supported?

See the Integration Library for a list of available source and target integrations.

What does a parameter on an integration setup page mean?

Each page in the Integration Library explains the integration’s setup parameters, including what each value does, why it is needed, and how to obtain it.