Skip to main content

​
Overview

This guide covers the common issues users encounter and provides steps to resolve them quickly. If your issue is not listed here, please contact support with details about your browser, operating system, and the steps taken before the issue occurred. To contact support in Sift, click your profile, and then click Customer Support.
If the issue occured during a Run, include a sharelink of the Run or Asset/Run ID.

​
Plot and visualization

These are the most common types of issues and are typically related to rendering, zooming, or large datasets.

​
Zoom does not work (X or XY zoom is unresponsive)

This usually happens when:
  • The dataset being plotted is very large
  • The plot has not fully finished loading
  • The browser is temporarily overloaded
  • FFT or high-resolution rendering is enabled
In some cases, the browser tab might appear frozen while processing data.

​
Plot freezes or browser tab locks up

This typically occurs when:
  • Plotting a very large time range
  • Viewing high-sample-rate data
  • Plotting many Channels simultaneously
  • Rendering FFT on large datasets
  • The browser might become temporarily unresponsive while processing.

​
Error after removing a Channel from a plot

This might occur when:
  • A removed Channel is still referenced in the plot state
  • A shared link contains outdated Channel references
  • A rendering state mismatch occurs after dynamic updates

​
Annotations obscure plotted data

Annotations might render above data layers, which can cause labels or markers to visually block parts of the timeseries.

​
Metadata box values appear swapped or incorrect

In rare cases, the UI rendering state might temporarily mismatch labels and values, particularly after zooming or rapid interactions.

​
Channel and layout issues

​
Long Channel names overlap or break layout

Very long Channel names might exceed the available UI width, leading to:
  • Overlapping text
  • Truncated names
  • Misaligned layout elements

​
Channel labels appear duplicated or formatted incorrectly

This might occur when:
  • Channel metadata includes overlapping naming attributes
  • Asset or Run information is appended multiple times
  • A UI formatting issue is triggered

​
Rule configuration issues

​
Rule shows “Error” instead of “Failure”

This occurs when the Rule itself is misconfigured, rather than the data violating a correctly written Rule.
  • Rules are written as CEL expressions. When Rule logic is discussed in this section, it is referring to CEL expression validity. See Rules overview.
  • See live Rule limitations.
There are two distinct outcomes when a Rule Runs:
  • Failure: The Rule logic is valid, but the data violates it.
  • Error: The Rule configuration is invalid or cannot execute properly.
An error state is typically caused by:
  • Invalid or incomplete Rule logic
  • Incorrect threshold expressions
  • Referencing fields or Channels that do not exist
  • Invalid arguments in Rule conditions
  • Unsupported comparison types
In these cases, the system cannot properly evaluate the Rule, so it enters an error state rather than reporting a failure.

​
Rule never evaluates or shows no results

If a Rule appears to never run, or produces no failures or results, it is often due to configuration scope rather than a system issue. Common causes include:
  • The Rule is attached to the wrong Asset
  • No data exists in the selected time range
  • The Rule is scoped to Runs that do not contain matching data
  • Filters or conditions prevent the Rule from executing
  • The Rule is not enabled or not associated with an active evaluation context