Model Failure due to Table Unavailability

Last updated on Aug 22, 2025
Applies To All SQL Models
Error Message Text(s) - ERROR: could not open relation with OID<number>
- Could not run model as there was another process running on table

Error Summary

This error occurs when a Model fails because the table used in its SQL query is unavailable during execution.

Potential Cause

Another Model creates and updates the table used in this Model’s SQL query. If that table is being truncated or loaded while the current Model tries to access it, the current Model fails.

For example, Model A uses Table B in its SQL query, which is created by another Model C. If Model C truncates or loads Table B while Model A tries to access it, the table becomes unavailable, causing Model A to fail.

Suggested Action(s)

Create a Workflow to schedule Models to run one after another.

Note: Starting Release 2.17, the Workflows feature is available only for existing users. Users signing up from Release 2.17 onwards cannot create Workflows.


Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Aug-22-2025 NA Added an error message for Model failure due to unavailability of the table used in its SQL query.
Aug-01-2025 NA New document.

Tell us what went wrong