# Detecting and Troubleshooting Broken Datasets and Monitors

**URL:** <https://community.observeinc.com/t/detecting-and-troubleshooting-broken-datasets-and-monitors/63>\
**Category:** Monitors & Alerts\
**Tags:** troubleshooting, kb\
**Created:** [August 27, 2025, 10:31pm UTC](https://community.observeinc.com/t/detecting-and-troubleshooting-broken-datasets-and-monitors/63 "2025-08-27T22:31:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nikhil.dua](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.observeinc.com/nikhil.dua/32/10_2.png) [@nikhil.dua](https://community.observeinc.com/u/nikhil.dua)\
**Post date:** [August 27, 2025, 10:31pm UTC](https://community.observeinc.com/t/detecting-and-troubleshooting-broken-datasets-and-monitors/63/1 "2025-08-27T22:31:13Z")

</div>

Sometimes dataset transformations (ongoing or backfill) can be suspended due to **system issues** or **performance problems**. Detecting these suspensions early will help you prevent unexpected data gaps.

* * *

## Types of Transforms

- **Ongoing** – processes new/real-time data.

- **Backfill** – reprocesses historical data.

Each type can suspend independently, so when reporting an issue, always specify:

- The **type of transform** (ongoing vs. backfill)

- Its **status**

* * *

## Monitoring for Suspended Transforms

You can detect suspended datasets using this OPAL query against the **System Datastream** :

```auto
make_col schema:string(EXTRA.schema)
filter schema = "transformer_suspended_transform"
make_col suspension_reason:string(FIELDS.suspension_reason)
make_col dataset_id:int64(FIELDS.dataset_id)
rename_col timestamp:BUNDLE_TIMESTAMP
set_link ^Dataset, dataset_id:@Observe_Dataset.dataset_id
pick_col timestamp, suspension_reason, dataset_id

```

This will return:

- **Timestamp** – when the suspension occurred

- **Suspension reason** – why it was suspended

- **Dataset ID** – link back to the dataset

* * *

## What to Do if Your Dataset Is Broken

If you discover a dataset suspension:

1. Check the **suspension reason**.

2. Refer to the decision table below to see if it’s something you can fix yourself.

3. If support is required, create a **support ticket** with:

* * *

## Suspension Reasons – Decision Table

| Suspension Reason | Can Fix Yourself? | Suggested Action |
| --- | --- | --- |
| **Ongoing acceleration is timing out** | ✅ (maybe) | Review transform definition, simplify queries, or contact Support. |
| **High compile times** | ✅ (maybe) | Simplify OPAL, reduce query complexity, or contact Support. |
| **Internal Snowflake errors (3000XX)** | 🚫 | Open a Support ticket with full error + timestamp. |
| **Admin-suspended** | 🚫 | Contact Support for more info. |

* * *

## More Details

### Self-Fixable Issues

- **Ongoing acceleration is timing out**

- **High compile times**

### Support-Required Issues

- **Acceleration runs into: ISE…**

- **SQL execution internal error: 3000XX…**

- **Admin console: …**

These are caused by system-level or vendor-related errors. Contact Support with the error details.

---

<div class="post-metadata">

**Author:** ![mlazzaro-better](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.observeinc.com/mlazzaro-better/32/56_2.png) [@mlazzaro-better](https://community.observeinc.com/u/mlazzaro-better)\
**Post date:** [September 5, 2025, 4:41pm UTC](https://community.observeinc.com/t/detecting-and-troubleshooting-broken-datasets-and-monitors/63/2 "2025-09-05T16:41:13Z")

</div>

Tested out the “suspended transforms” query in my account, and I’m seeing a couple of entries over the last 30 days with the following `suspension_reason`

> acceleration stuck with error: statement 0 failed: 002003 (42S02): SQL compilation error: Object ‘DOES\_NOT\_EXIST’ does not exist or not authorized. (EXECUTION)

I know we’ve deleted a few datasets over that same period, is this maybe a normal thing that happens when the acceleration is stopped when a dataset is deleted, or something like that?

I don’t think we’ve had any issues with any of the datasets that are still in use, so I’m assuming this is safe to ignore.

---

<div class="post-metadata">

**Author:** ![nikhil.dua](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.observeinc.com/nikhil.dua/32/10_2.png) [@nikhil.dua](https://community.observeinc.com/u/nikhil.dua)\
**Post date:** [September 5, 2025, 9:45pm UTC](https://community.observeinc.com/t/detecting-and-troubleshooting-broken-datasets-and-monitors/63/7 "2025-09-05T21:45:42Z")

</div>

Looking further, the error was due to merge transforms taking place on 2 of the datasets.

Upon double-checking these, they can be safely ignored as no acceleration jobs are stuck and had continue successfully automatically after that error took place!