Hi there,
We have a critical materialization that is currently blocked and affecting downstream transforms. The materialization for our core object, has been stuck for approximately 24 hours. We are unable to resolve this by triggering new builds or adjusting the build configuration.
Problem
- Context: We have a core object “Activity”, which is indexing in Ontology Manager but not materializing. We have a high volume of daily object edits, object size is about 2M records, 270 properties. The object continues to index successfully to OSv2, Automate and OQL.
- Impact: The materialization is a dependency for several critical downstream transforms/datasets, which are now failing to update.
- Current Status: The materialization is showing a status of “Hydrating” but has not successfully built in over 24 hours. New manual builds or configuration changes (Rebuild with latest definition, Edit configuration) do not seem to take effect. Upon reviewing the build history, we see the build stuck on Queued (full steps Queued, Waiting, Running, Succeeded, Failed). When clicking a Queued button for the job, it’s unable to show the job that this build is queued behind, with “Error loading job”.
Debugging Steps Taken
We have already attempted the following to resolve:
- Manually triggered new builds.
- Adjusted the build interval configuration
- Checked upstream backing dataset and object
- Checked downstream transforms (all are failing due to this object).
Request for Assistance
Please help us unblock the materialization of this object, or point us to how we can investigate the root cause of the “Error loading job” build. Any guidance on how to debug or force-resolve this specific build block would be greatly appreciated.