Data Quality & Observability limitations

August 20, 2026

The following table identifies known Data Quality & Observability (cloud) limitations.

Topic	Known limitation	Description
About data quality monitors	Cancel icon not shown on the Monitors tab run history chart	When you cancel a job, the run history chart on the Monitors tab shows the canceled run using a standard point marker. The cancel icon shown in other parts of the interface, such as the Profile tab run history, is a custom SVG icon that cannot be rendered on the Monitors chart, because the chart uses point markers connected by continuous lines and the charting library does not support custom SVG injection in this configuration. The canceled run status is still reported correctly. Only the visual icon differs between the Monitors chart and other UI locations.
Create a Pullup job Create a Pushdown job	TIMESTAMP column filters with time components not supported on Oracle connections	When you add a filter on a TIMESTAMP column and the filter value includes a time component (for example, 2026-03-23 03:00:00), the job fails at runtime. The generated filter query does not apply timestamp casting to the value, so Oracle cannot resolve the comparison. To avoid this issue, enter the filter value as a complete timestamp in the format Oracle expects, including the time component. For example, rather than entering 2026-03-23, enter 2026-03-23 00:00:00.

Topic

Known limitation

Description

About data quality monitors

Cancel icon not shown on the Monitors tab run history chart

When you cancel a job, the run history chart on the Monitors tab shows the canceled run using a standard point marker. The cancel icon shown in other parts of the interface, such as the Profile tab run history, is a custom SVG icon that cannot be rendered on the Monitors chart, because the chart uses point markers connected by continuous lines and the charting library does not support custom SVG injection in this configuration.

The canceled run status is still reported correctly. Only the visual icon differs between the Monitors chart and other UI locations.

TIMESTAMP column filters with time components not supported on Oracle connections

When you add a filter on a TIMESTAMP column and the filter value includes a time component (for example, 2026-03-23 03:00:00), the job fails at runtime. The generated filter query does not apply timestamp casting to the value, so Oracle cannot resolve the comparison.

To avoid this issue, enter the filter value as a complete timestamp in the format Oracle expects, including the time component. For example, rather than entering 2026-03-23, enter 2026-03-23 00:00:00.