PRQL-XXXX format. Codes are shared across Prequel Import and Prequel Export, so the table below is the same reference you will find in the Export docs, and it includes codes that only apply to exports.
Where codes appear
- Extracts and loads
- Records
A failed extract or load carries a full
error object.Error object on an extract or load
{
"error": {
"error_code": "PRQL-KFSS",
"title": "Source Circuit Breaker Tripped",
"blame": "first_party",
"documentation_url": "https://docs.prequel.co/export/error-handling/error-codes",
"message": "The job encountered too many source mapping, transform, or validation errors and triggered the circuit breaker. Execution was halted early to protect system resources. Please review the failed records to determine the root cause.",
"trace": "..."
}
}
Individual records report a narrower shape. Each stage of a record’s lifecycle reports its own
error_code and error_trace, so you can tell whether a record failed during extract, transform, validate, acknowledge, or load.Error on a record stage
{
"error": {
"error_code": "PRQL-RSLM",
"error_trace": "..."
}
}
blame value means, see Coded error handling in the Export docs.
Code reference
| Code | Title | Message |
|---|---|---|
| PRQL-RZBD | All Records Errored | None of the source provided rows were processed successfully. Please review the error records to determine the cause of the failure. |
| PRQL-BNOD | Athena Authorization Failed | The Athena engine encountered an error. Please check that the provided connection principal has been granted sufficient permissions. Specifically, please check the s3:ListBucket permission. |
| PRQL-DDAK | Athena Authorization Failed | The Athena engine encountered an error. Please check that the provided connection principal has been granted sufficient permissions. Specifically, please check for Create Database on Catalog permission. |
| PRQL-FDEW | Athena Authorization Failed | The Athena engine encountered an error. Please check that the provided connection principal has been granted sufficient permissions. |
| PRQL-RWCV | Athena Authorization Failed | The Athena engine encountered an error. Please check that the provided connection principal has been granted sufficient permissions. Specifically, please verify the glue:DeleteTable permission exists on the generated tables. |
| PRQL-VDMC | Athena Authorization Failed | The Athena engine encountered an error. Please check that the provided connection principal has been granted sufficient permissions. Specifically, please check the s3:GetObject permission. |
| PRQL-XZWE | Athena Cannot Find Requested Iceberg Entity | Athena has detected a corrupted Iceberg table. Full refresh to resolve. |
| PRQL-ONNN | Athena Connection Refused | The Athena connection was refused. Please check that the provided Athena access details are correct. |
| PRQL-QDPO | Athena DDL Execution Timeout Error | The Athena query exceeded the engine’s DDL query timeout. If this error persists, please contact support. |
| PRQL-XJWM | Athena Data Catalog Timeout Error | The Athena data catalog connection timed out. If this error persists, please contact support. |
| PRQL-AFOK | Athena Data Processing Failed | The Athena engine encountered a ConcurrentModificationException while executing a query. |
| PRQL-AWRI | Athena Data Processing Failed | The Athena engine encountered a problem while attempting to process Iceberg formatted data. |
| PRQL-BKDL | Athena Data Processing Failed | The Athena query engine encountered an error. A value found in the underlying source data is incompatible with the type double defined in the Athena table schema. Please review the source’s data type and either cast the type or update your Prequel data model accordingly. |
| PRQL-BSAX | Athena Data Processing Failed | The Athena engine encountered an error related to the timestamp precision on some timestamp data. |
| PRQL-CFGX | Athena Data Processing Failed | The Athena engine encountered a problem while attempting to process data in hive mode. |
| PRQL-FLUU | Athena Data Processing Failed | The Athena engine encountered a problem while attempting to process Iceberg formatted data. |
| PRQL-GVZM | Athena Data Processing Failed | The Athena engine encountered a problem while attempting to process Hive formatted data. |
| PRQL-CERZ | Athena Federated Read Error | Athena encountered an exception reading from a federated data source. Please refer to Athena logs for more information. |
| PRQL-KXAL | Athena Glue Data Catalog Rate Limit Exceeded | AWS throttled Glue Data Catalog API requests for this Athena connection. This is usually transient; please retry, and reduce concurrent Athena operations if it persists. |
| PRQL-DJDS | Athena Glue Metastore Operation Timeout | The Glue Data Catalog timed out fetching table metadata for the Athena source. Please review Glue API usage from concurrent operations, reduce contention if possible, and if necessary, request an increase in service quota. |
| PRQL-JNZR | Athena IAM Role Token Audience Mismatch | AWS rejected the federated identity token because its audience did not match what the IAM role expects. Please verify the oaud condition in the role’s trust policy matches the provided value. |
| PRQL-YOTO | Athena Iceberg Partitions Exceeded | The Athena engine exceeded the maximum number of open partition writers. Please contact support for more information. |
| PRQL-IVCA | Athena Invalid Cast Argument | One or more column was unable to be cast to the data type from the corresponding model. Please ensure that are source column data types are compatible with model data types and try again. |
| PRQL-MSQX | Athena Invalid Date Value | Athena could not cast a data value to type DATE. Check the source data to ensure dates are in the format YYYY-MM-DD. |
| PRQL-TKVM | Athena Invalid Timestamp Value | Athena could not cast a data value to type TIMESTAMP. Check the source data to ensure the data can be properly cast into timestamp or determine if it requires additional handling. |
| PRQL-LFDR | Athena Lake Formation Permissions Error | The connection encountered one or more Lake Formation permissions errors. Please ensure any Lake Formation policy contains sufficient permissions and try again. Contact support if the issue persists. |
| PRQL-LRCT | Athena Lambda Timeout | Athena encountered an exception reading from a federated data source. A lambda function timed out. |
| PRQL-CKSC | Athena Missing Column | The Athena query engine encountered an error. A column name was not recognized. |
| PRQL-KZWP | Athena NOT NULL Value Constraint Failed | A NULL value was found in a column with non-null requirements. Please check the model’s columns designated as is_primary_key and is_last_modified for any null values in your source. |
| PRQL-XIEA | Athena Query Timeout | The Athena query execution timed out. If this error persists, please contact support. |
| PRQL-NXQP | Athena Read Error | The Athena engine encountered a problem while attempting to read the source view. Please confirm the view is not stale. |
| PRQL-FJOD | Athena Runtime Encountered Error | The provided AWS role does not have access to the Athena Workgroup. If the Athena Workgroup does not exist, the provided role does not have permission to create the workgroup. |
| PRQL-TJCZ | Athena Runtime Encountered Error | The Athena connection encountered a memory limit. |
| PRQL-VKEV | Athena Runtime Encountered Error | The Athena catalog encountered an internal server error. If this error persists, please contact support. |
| PRQL-WJTE | Athena Runtime Encountered Error | The Athena connection encountered an error. |
| PRQL-WRFA | Athena Runtime Encountered Error | The Athena engine encountered an error. |
| PRQL-YTNS | Athena Runtime Encountered Error | The Athena connection encountered a resource limit. |
| PRQL-ASFB | Athena S3 Access Denied | The provided credentials were denied access to the S3 source bucket. Please check that the IAM role has s3:GetObject, s3:ListBucket, and s3:GetBucketLocation granted on the source bucket and its contents. |
| PRQL-CMYT | Athena Schema Does Not Exist Error | The Athena schema could not be found. Please check that the schema exists and that the provided connection principal has been granted sufficient permissions. |
| PRQL-HDXP | Athena Server Encountered Generic Error | The Athena connection encountered a generic internal error. If this error persists, please contact support. |
| PRQL-KLBO | Athena Server Encountered Internal Error | The Athena connection encountered an internal error. If this error persists, please contact support. |
| PRQL-GAIX | Athena Table Missing | The Athena query engine encountered an error. The table name was not recognized. |
| PRQL-MZXD | Athena Table Not Found | The Athena engine could not find the table to read from or merge into. Please verify that the table exists and the connection principal has been granted sufficient permissions. |
| PRQL-XYYX | Athena Type Mismatch | Athena attempted to use an operator on values of differing types. Please check the source query for type mismatches. |
| PRQL-WHHO | Athena Unable To Assume Role | Athena was unable to assume the specified role. Please verify the role ARN. |
| PRQL-VMEX | Athena Unsupported Timestamp Precision Error | Athena source data of type “timestamp(6)” is unsupported. Please expose the column as type “timestamp(3)”. |
| PRQL-QTSM | Athena Unsupported Timestamp Type Error | Athena source data of type “timestamp with time zone” is unsupported. Please expose the column as type “timestamp”. |
| PRQL-MDSR | Azure Authorization Expired | The Azure server returned an error indicating the access token is expired. Please check that the provided shared access key is valid and has been granted sufficient permissions. |
| PRQL-BFKH | Azure Blob Snapshots Prevented Delta Table Cleanup | A file in the destination bucket could not be deleted because it has blob snapshots. Please first delete all snapshots of blobs under the table prefix, and ensure soft deletes are disabled on the storage account. Then, try again. |
| PRQL-ZDJR | Azure Blob Storage Authentication Failed | Azure Blob Storage encountered an error. Please check that the provided connection principal has been granted sufficient permissions. |
| PRQL-UXWZ | Azure Blob Storage Authorization Error | Azure Blob Storage returned an authorization error. Please verify your SAS token includes the required permissions on the target Container and has not expired. If network access is restricted on the storage account, ensure the service egress IP is in the allowed range. |
| PRQL-GJWR | Azure Blob Storage Host Not Found | The Azure Blob Storage host could not be found. Please check that the provided host name is valid. |
| PRQL-VMDR | Azure Blob Storage Invalid SAS Token | Azure Blob Storage could not authenticate the request. Please verify you have generated an SAS token (access keys are not supported), your SAS token has not expired, and was copied correctly, then try again. |
| PRQL-YZQZ | Azure Databricks Storage Request Not Authorized | The Azure Databricks storage request failed authorization. The storage account’s ‘Firewalls and virtual networks’ settings may be blocking access to storage services. Please verify your Azure storage credentials or firewall exception settings. |
| PRQL-JRKJ | BigQuery Authentication Failed | The BigQuery connection was refused. Please check that that the provided connection principal has been granted sufficient access. |
| PRQL-PVER | BigQuery Authentication Failed | The BigQuery connection was refused. Please check that that the provided connection principal has been granted sufficient access. |
| PRQL-SPJT | BigQuery Authentication Failed | The BigQuery server rejected the connection. Please check that the provided authentication principal and credentials are valid. |
| PRQL-AVSM | BigQuery Avro File Schema Mismatch | An Avro file backing this BigQuery table is missing a column the table schema requires. Please check the pipeline writing the table’s underlying files, or add a default value for the column. |
| PRQL-UJSZ | BigQuery Column Already Exists | The BigQuery engine encountered an error. The target column name already exists. |
| PRQL-NIKQ | BigQuery Column Does Not Exist | The BigQuery engine encountered an error. The target column name is unrecognized. |
| PRQL-BJRB | BigQuery Column Rejected Null Value | A column in the destination table is marked REQUIRED but received a null value. This can occur when a column present in the destination table is missing from the write. Please contact support for more information. |
| PRQL-VKGX | BigQuery Column Type Mismatch | One or more column’s data type does not match the existing destination column. Please verify all destination table column types match the types defined in the corresponding model. |
| PRQL-UCFB | BigQuery Connection Refused | The provided Google Cloud project has not enabled BigQuery. |
| PRQL-CQEX | BigQuery Custom Query Quota Exceeded | A custom BigQuery query usage quota set by your administrator was exceeded. Please raise the quota or wait for it to reset. |
| PRQL-FGWV | BigQuery Data Processing Failed | The BigQuery data transfer encountered an error during data transfer. The BigQuery target table may have duplicate data preventing successful updates. |
| PRQL-JEBJ | BigQuery Dataset Not Found | The specified BigQuery dataset was not found in the configured project and region. Please verify the dataset name and region provided and try again. |
| PRQL-TIRE | BigQuery Disallowed Bucket Retention Policy | Bucket and object retention policies are disallowed on BigQuery staging policies. Please remove the policy or use a bucket without a retention policy. |
| PRQL-ZVKN | BigQuery GCS Authentication Error | The service account does not have sufficient access to the GCS bucket. Please review the list bucket permissions provided via IAM roles. |
| PRQL-BRLC | BigQuery Invalid Bucket Region | The provided GCS bucket region is invalid. Please ensure the specified region field is exactly one of the following valid GCS bucket location names: https://docs.cloud.google.com/storage/docs/locations. |
| PRQL-WMRB | BigQuery Rate Limit Exceeded | One or more queries has exceeded a BigQuery rate limit. Please contact support for more information. |
| PRQL-PWQD | BigQuery Runtime Encountered Error | The BigQuery connection encountered an error. |
| PRQL-GKCB | BigQuery Server Encountered Error | The BigQuery API was temporarily unavailable (HTTP 503). This is typically a temporary issue and resolves automatically. If the error persists, check the Google Cloud status page to confirm service health. |
| PRQL-FGCV | BigQuery Service Account Disabled | The BigQuery connection was refused because the configured service account has been disabled. Please re-enable the service account in GCP IAM & Admin, or create a new service account and update configuration details. Then, try again. |
| PRQL-AEVP | BigQuery Table Not Accessible | The user does not have permission to query the specified BigQuery Table, or it was not found in the configured region and dataset. Please review the user’s permissions on the table and dataset, and the region and dataset names provided. |
| PRQL-MJOZ | ClickHouse Connection Refused | The provided ClickHouse host was not found. Please check that the provided host name is valid and accessible. |
| PRQL-OEVX | ClickHouse Connection Refused | The provided ClickHouse host was not found. Please check that the provided host name is valid and accessible. |
| PRQL-UFTZ | ClickHouse Connection Refused | The provided ClickHouse host refused the connection. Please check that the provided host name is valid and accessible. |
| PRQL-WKVZ | ClickHouse Connection Timed Out | The connection to the ClickHouse host timed out. Please check that the host and port are reachable and that the static IP address (or addresses) are allowlisted in your security group/firewall. |
| PRQL-CTBL | ClickHouse Insufficient Create Table Permissions | The ClickHouse user does not have permission to create tables. Please ensure both CREATE TABLE and CREATE TEMPORARY TABLE are granted to the ClickHouse user on the target database and try again. |
| PRQL-BKFC | ClickHouse Insufficient Read Permissions | The ClickHouse user does not have permission to read from the data tables and/or schema. Please ensure to grant SELECT on the database, tables for sync, and information_schema and try again. |
| PRQL-DSAJ | ClickHouse Insufficient S3 Staging Bucket List Permissions | The ClickHouse instance was denied access to the S3 staging bucket while checking whether a staged file exists before writing. Please check that you have provided the s3:ListBucket permission on the staging bucket itself (without any key prefix added), and try again. |
| PRQL-WKRF | ClickHouse Insufficient S3 Write Permissions | The ClickHouse user cannot write to the S3 staging bucket. Please grant the S3 write permission to the ClickHouse user with GRANT S3 ON . to <username>@’%’ (or GRANT WRITE ON S3 if your instance uses granular enable_read_write_grants) and try again. |
| PRQL-BNPN | ClickHouse Insufficient View Permissions | The ClickHouse user does not have permissions to create and/or drop views generated during transfers. Please grant CREATE VIEW and/or DROP VIEW to the ClickHouse user on the target database and try again. |
| PRQL-SKFD | ClickHouse Invalid Connection Parameter | The provided ClickHouse credentials contain an invalid character. Please check that the username and password do not contain special characters such as @, /, or ?. |
| PRQL-UQKO | ClickHouse Memory Limit Exceeded | The ClickHouse instance ran out of memory while exporting data. Please scale up the service’s maximum memory limit and try again. |
| PRQL-XCNS | ClickHouse Rate Limited | The Clickhouse server encountered a resource quota limit for simultaneous queries. |
| PRQL-ZXEC | ClickHouse TLS Certificate Expired | The ClickHouse endpoint presented an expired TLS certificate. Please renew the certificate on the server or proxy terminating TLS and try again. |
| PRQL-VCXL | Clickhouse Invalid Truncate Permissions | The Clickhouse engine encountered an error. Please check that the provided user has been granted sufficient permissions to truncate tables. |
| PRQL-NJEW | Data Serialization Error | One or more rows from the source cannot be parsed. This may be caused by a row exceeding byte size limits, invalid/non-supported encoded characters, unquoted values, or column errors. Please contact support for more information. |
| PRQL-BKRG | Databricks Authorization Failed | The provided service principal is not authorized to use the SQL endpoint. Please confirm that the service principal is listed as an authorized user with Can Use within the SQL Warehouse permissions, and try again. |
| PRQL-AXJS | Databricks Catalog Not Found | The specified Databricks catalog was not found. Please check the catalog name in the connection configuration exists in the target workspace and try again. |
| PRQL-CJFX | Databricks Catalog Permission Denied | The Databricks connection was refused due to insufficient catalog permissions. Please check that the provided connection principal has been granted USE CATALOG permission on both the target catalog and Databricks system catalog, then try again. |
| PRQL-CSVN | Databricks Concurrent Write Conflict | The Databricks server encountered a concurrent update to the target table. Please ensure no other INSERT, DELETE, UPDATE, or MERGE queries are running. |
| PRQL-LADF | Databricks Connection Closed Prematurely | The Databricks connection closed before the statement finished executing. Check the Databricks status page and confirm the target SQL warehouse is running and reachable. |
| PRQL-MKEW | Databricks Connection Temporarily Rejected | The Databricks connection was temporarily rejected because the service is under maintenance. |
| PRQL-ZQAC | Databricks Delta Table Metadata Missing From Storage | One or more Delta table transaction log files are missing from the underlying storage bucket. Please check bucket lifecycle policies to ensure no files are deleted, and contact support to learn more. |
| PRQL-LRXO | Databricks Destination Table Missing Model Column | The destination table is missing a column the model expects. Please restore the column or run a full refresh to rebuild the table. |
| PRQL-WBZK | Databricks Destination Table Ownership Required | The connection principal does not own the destination table. Please transfer ownership of the table to the connection principal, then retry. |
| PRQL-VIDE | Databricks Duplicate Row Error | The Databricks data transfer encountered an error during data transfer. The Databricks target table or staged data may have duplicate data preventing successful updates. Please confirm there is no duplicate data in the data source, and contact support if the issue persists. |
| PRQL-IPBL | Databricks IP Access List Restriction | The Databricks connection was blocked by an IP access list restriction at the Databricks account or workspace-level. Please ensure any configured IP access lists include the data sync service’s static egress IP(s). |
| PRQL-JMES | Databricks Identity Not Assigned To Workspace | The connection principal is not a member of the targeted Databricks workspace. Please confirm the user or service principal is assigned to that workspace and that the configured host points to the correct workspace, then try again. |
| PRQL-XTZH | Databricks Insufficient Credits Available | The connection to Databricks could not be established as the Databricks account has insufficient credits. Please add a payment method or purchase additional credits. |
| PRQL-OLKS | Databricks Internal Query Failure | Databricks reported an internal error while executing the query. Please check the Databricks status page and retry. |
| PRQL-JZQZ | Databricks Invalid Access Token | The Databricks connection was refused due to an invalid access token. Please check that the access token (dapi...) is valid and the provided connection principal has been granted sufficient access. |
| PRQL-OAUT | Databricks Invalid OAuth Credentials | The Databricks connection was refused because the OAuth client credentials were rejected. Please verify that the Client ID and Client Secret are correct and the credential has not expired, then please try again. |
| PRQL-QOCK | Databricks Java IO Error Encountered | Databricks encountered an I/O error while executing the operation. Review the Databricks query/driver logs and the Databricks status page to identify the failure. |
| PRQL-VIZF | Databricks Network Error Encountered | The connection to Databricks was dropped unexpectedly. Check the Databricks status page and confirm the target SQL warehouse is running and reachable. |
| PRQL-FUOM | Databricks Operation Not Supported | The Databricks server encountered an error. Please check that the provided connection principal has been granted sufficient access. |
| PRQL-QWEO | Databricks Query Timeout | The Databricks query connection timed out. If this error persists, please contact support. |
| PRQL-CKSR | Databricks Rate Limit | The Databricks server encountered a rate limit. If this error persists, please contact support. |
| PRQL-CYNR | Databricks Runtime Error Encountered | Databricks could not schedule the query and returned a temporary error (HTTP 503) asking to retry. This usually resolves on the next run. If the error persists, check the Databricks status page and the target SQL warehouse’s health and load. |
| PRQL-GMXD | Databricks Runtime Error Encountered | The Databricks server does not have Predictive Optimization enabled. |
| PRQL-INXB | Databricks Serverless Warehouse Disabled | The Databricks warehouse cannot start because serverless warehouse compute is disabled in the global warehouse configuration. Please contact your Databricks administrator to enable compute for serverless warehouses, and try again. |
| PRQL-YBLK | Databricks Service Unavailable | Databricks returned a 503 Service Unavailable response. This may be caused by Databricks SQL warehouse autoscaling, startup delays, warehouse load, or a transient Databricks service issue. Please check that both the target SQL warehouse and Databricks servers are healthy, and try again. |
| PRQL-CMRT | Databricks Storage Authorization Failure | Databricks failed to execute one or more staging upload queries with PUT. If using Unity Catalog, please ensure the Write Volume permission has been provided to the Service Principal or user. If using Hive Metastore, please ensure write and delete permissions have been provided on the object storage location. |
| PRQL-BUMS | Databricks Table Or View Not Found | A referenced table or view was not found. Please check that the target tables were not dropped or renamed. |
| PRQL-PSZD | Databricks Warehouse Stopped | The Databricks transfer failed because the target warehouse was stopped. |
| PRQL-YWEX | Databricks Workspace Rate Limit Exceeded | The Databricks workspace exceeded its API rate limit. Please retry later, reduce concurrent requests, and/or contact Databricks to increase request limits in the workspace. |
| PRQL-DBSH | Databricks no such host | Connection to Databricks could not be established on failure to reach host. Please ensure that the provided hostname is accurate and the Databricks cluster is publicly accessible. |
| PRQL-DLDQ | Delta Lake Duplicate Row Error | One or more duplicate rows have been detected in the source data. Please ensure that each row’s primary key is unique/de-duplicated and retry. |
| PRQL-WKXN | Delta Lake Engine Stopped Unexpectedly | The Delta Lake engine stopped unexpectedly during the transfer. Please retry the transfer. If this error persists, please contact support. |
| PRQL-UFQE | Delta Lake Object Not Found | The Delta Lake engine could not find an object. Make sure the object exists and the writer has read access to the bucket. |
| PRQL-GFIS | Delta Lake Runtime Error | The Delta Lake engine encountered an error. |
| PRQL-CISE | Delta Lake Table Creation Failed | The delta lake table could not be created due to existing conflicting metadata in the bucket prefix. |
| PRQL-GTRI | Delta Lake Transaction Log Commit Failed | The transaction log could not be committed to the destination bucket. This is most commonly caused by failing to disable soft delete defaults on the storage account. Please first check that both blob and container soft deletes are disabled on the storage account, then ensure no other engines write to the table concurrently before retrying. |
| PRQL-BERH | Destination Table Not Found | The destination table was not found in the target schema. Please ensure the destination table exists at the configured schema and with the target table name. Contact support for more information. |
| PRQL-DOOM | DuckDB Out of Memory | The transfer worker ran out of memory. If this error persists, please contact support. |
| PRQL-PZCR | Federated Token Exchange Rejected | Google rejected the identity provider’s token during the workload identity federation exchange. Verify the workload identity pool and provider settings, including the allowed audience, and that the identity provider issues JWT access tokens. |
| PRQL-QGBC | GCS Bucket Not Found | A GCS bucket under the configured bucket name and region could not be found in the target GCP project. Please check that the name and region are set correctly, create the bucket if it does not already exist, then try again. |
| PRQL-SLVK | GCS Missing Bucket Storage GET Permission | The GCS server encountered an error due to insufficient permissions. Please check that the provided connection principal has been granted ‘storage.buckets.get’. |
| PRQL-ZQZQ | GCS Missing Create Permission | The GCS server encountered an error due to insufficient permissions. Please check that the provided connection principal has been granted ‘storage.objects.create’. |
| PRQL-AYSD | GCS Missing Delete Permission | The GCS server encountered an error due to insufficient permissions. Please check that the provided connection principal has been granted ‘storage.objects.delete’. |
| PRQL-KJCH | GCS Server Encountered Error | Google Cloud Storage returned an internal server error (HTTP 500). This is typically a temporary issue and resolves automatically. If the error persists, check the Google Cloud status page to confirm service health. |
| PRQL-NXPY | GCS Server Encountered Error | Google Cloud Storage was temporarily unavailable (HTTP 503). This is typically a temporary issue and resolves automatically. If the error persists, check the Google Cloud status page to confirm service health. |
| PRQL-IXOL | Google Sheets Authentication Failed | The Google Sheets server refused the connection. |
| PRQL-NEFP | Google Sheets Authentication Failed | The Google Sheets server refused the connection. |
| PRQL-VDJX | Google Sheets Data Processing Failed | The Google Sheets server encountered a temporary error and the connection was dropped. If this error persists, please contact support. |
| PRQL-LNWT | Google Sheets Host Not Found | The Google Sheets host could not be found. Please check that the provided host name is valid. |
| PRQL-CELL | Google Sheets Overloading Error | A Google Sheet may not have more than 10,000,000 cells. If the error persists, please choose another destination type. |
| PRQL-BOSR | Google Sheets Server Encountered Error | Google Sheets returned a bad gateway error (HTTP 502). This is typically a temporary issue and resolves automatically. |
| PRQL-CMET | Google Sheets Server Encountered Error | Google Sheets was temporarily unavailable (HTTP 503). This is typically a temporary issue and resolves automatically. If the error persists, check the Google Workspace status page to confirm service health. |
| PRQL-GPDB | Google Sheets Server Encountered Error | Google Sheets returned an internal server error (HTTP 500). This is typically a temporary issue and resolves automatically. |
| PRQL-YICW | Google Sheets Server Encountered Error | The Google Sheets server encountered a resource quota limit. |
| PRQL-ICED | Iceberg Authorization Failed | A query failed due to insufficient database permissions. Please check that the provided connection details are correct and the principal has been granted sufficient permissions to the target catalog and object store. |
| PRQL-FJVY | Identity Provider Rejected Client Credentials | The identity provider rejected the configured OAuth client credentials (invalid_client). Verify the client ID and client secret and try again. |
| PRQL-BVHD | Identity Provider Token Fetch Failed | Prequel could not fetch an OAuth token from the configured identity provider token endpoint. Verify the token endpoint URL is publicly reachable over https and that it accepts the configured client credentials. |
| PRQL-BBGU | Import Artifact Staging Error | Prequel could not stage the batch file for delivery. The records were not sent and will be retried on the next load. |
| PRQL-NSCH | Import Dataset Schema Unavailable | The dataset schema is unavailable until an extract has successfully extracted rows for this dataset. |
| PRQL-MLAI | Import Delivery Outcome Integrity Error | Prequel detected an internal inconsistency while recording delivery results. The affected records were not marked delivered and will be retried on the next load. Please contact support if this persists. |
| PRQL-QPMF | Import Destination Bad Gateway | The destination endpoint returned HTTP 502. Undelivered records are retried on the next scheduled load. |
| PRQL-JPDQ | Import Destination Bad Request | The destination endpoint rejected the record with HTTP 400. Check the record data and destination configuration. |
| PRQL-IMEK | Import Destination Client Error | The destination endpoint rejected the record with a client error (4xx). Check the destination configuration and record data. |
| PRQL-KTQN | Import Destination Connection Refused | The destination endpoint refused the connection. Verify the URI and that the endpoint is accepting connections. |
| PRQL-YCHU | Import Destination Context Cancelled | The delivery operation was cancelled before all records could be delivered. Undelivered records will be retried on the next load cycle. |
| PRQL-FVRM | Import Destination DNS Error | DNS resolution failed for the destination endpoint. Verify the hostname in the destination URI. |
| PRQL-CNJK | Import Destination Forbidden | The destination endpoint returned HTTP 403. Verify webhook signature configuration and credentials. |
| PRQL-PRHQ | Import Destination Gateway Timeout | The destination endpoint returned HTTP 504. If the response carried a Retry-After header the request was retried immediately, otherwise the record will be retried on the next scheduled load. |
| PRQL-QFJW | Import Destination Headers Too Large | The destination endpoint returned HTTP 431. Reduce the number or size of custom headers in the request template. |
| PRQL-PHOK | Import Destination Internal Server Error | The destination endpoint returned HTTP 500. Undelivered records are retried on the next scheduled load. If the error persists, check the destination endpoint health. |
| PRQL-TWER | Import Destination Invalid Acknowledgement | The destination acknowledgement payload was malformed or failed schema validation. |
| PRQL-HWLT | Import Destination Network Error | A network error occurred while delivering a record to the destination endpoint. Check the destination URI and network connectivity. |
| PRQL-VFTB | Import Destination Not Found | The destination endpoint returned HTTP 404. Verify the URI in the request template. |
| PRQL-QAHC | Import Destination Payload Too Large | The destination endpoint returned HTTP 413. Reduce the record size or adjust the destination’s payload limits. |
| PRQL-WQKF | Import Destination Rate Limited | The destination endpoint rate-limited the request (HTTP 429). If the response carried a Retry-After header the request was retried immediately, otherwise the record will be retried on the next scheduled load. |
| PRQL-EZDQ | Import Destination Request Error | Failed to construct the HTTP request for the destination endpoint. Check the destination configuration. |
| PRQL-TNXG | Import Destination Server Error | The destination endpoint returned a server error (5xx). Undelivered records are retried on the next scheduled load. If the error persists, check the destination endpoint health. |
| PRQL-HNNX | Import Destination Service Unavailable | The destination endpoint returned HTTP 503. If the response carried a Retry-After header the request was retried immediately, otherwise the record will be retried on the next scheduled load. |
| PRQL-XNWB | Import Destination TLS Error | TLS handshake failed with the destination endpoint. Verify the endpoint supports HTTPS and has a valid certificate. |
| PRQL-BXPM | Import Destination Template Error | The destination request template is misconfigured. Verify that the body template syntax is valid and all referenced fields exist in the destination’s record schema. |
| PRQL-GMVJ | Import Destination Timeout | The request to the destination endpoint timed out. Undelivered records are retried on the next scheduled load. If the error persists, check the destination endpoint latency. |
| PRQL-NROT | Import Destination Unprocessable Entity | The destination endpoint returned HTTP 422. The record data is syntactically valid but semantically incorrect. |
| PRQL-NBSI | Import Job Cancelled | The import job was cancelled. Please retry — or contact support if you did not initiate this and the issue persists. |
| PRQL-VXPK | Import Primary Key Not String | The primary key column must be of type string (text/varchar). Please ensure the source table primary key column is string-typed. |
| PRQL-KVZK | Import Provider Not Configured | No enabled import provider is available for this request. Create one with POST /import/providers or enable an existing provider before creating datasets, extracts, or loads. |
| PRQL-WCKH | Import Transform Invalid Configuration | A stream mapping configuration was invalid or missing required fields like ‘name’ or ‘target_field’. |
| PRQL-BKDX | Import Transform Invalid Payload | The transformation pipeline encountered an invalid JSON payload. Please ensure that stream records are valid JSON. |
| PRQL-TRUN | Import Transform Runtime Error | The transformation pipeline encountered one or more runtime errors. Please review the mapping expressions and input data. |
| PRQL-NOTD | Import Transform Unsupported Mapping | An unsupported mapping type was used in stream configuration. Supported types are ‘field’ and ‘expr’. |
| PRQL-VKHA | Import Transform Validation Failed | A stream record failed validation against the destination record schema after transformations were applied. |
| PRQL-OHHG | Import Worker Unavailable | No import worker is currently available to process this request. The system will auto-recover shortly. Please retry. |
| PRQL-INUM | Invalid Input: Numerical Type | One or more values could not be cast to a numerical type. Please ensure all source data columns of numerical types contain valid numerical values. Contact support if this error persists. |
| PRQL-FGAD | Invalid Timestamp Value in Source Column | An invalid timestamp value was detected in a source column. Please review your timestamp columns for invalid values. |
| PRQL-XTQZ | Missing Datalake Cache Resource | The dataset’s cached data was not found in its datalake. Ensure the dataset belongs to a provider whose datalake bucket remains active and intact, and try again. |
| PRQL-CLNU | MongoDB Authentication Failed | The MongoDB connection was refused due to insufficient permissions. Please check that the provided connection principal has been granted sufficient access. |
| PRQL-KWZN | MongoDB Authentication Failed | The MongoDB connection was successful, but the user is not authorized. Please check that the provided user has access. |
| PRQL-MJUM | MongoDB Authentication Failed | The MongoDB connection was refused. Please check that the provided MongoDB access details are correct. |
| PRQL-FBNN | MongoDB Collection Not Found | The provided MongoDB collection was not found. |
| PRQL-BGZS | MongoDB Connection Failed | The MongoDB connection was unsuccessful due to an unexpected configuration error. If the error persists, please contact support. |
| PRQL-KDCW | MongoDB Connection Refused | The MongoDB connection was refused. Please check that the provided MongoDB server is valid and accessible. |
| PRQL-MDXE | MongoDB Runtime Encountered Error | The MongoDB connection exceeded a space quota. |
| PRQL-VIPD | MongoDB Runtime Encountered Error | The MongoDB connection encountered a memory limit. |
| PRQL-OPXQ | MotherDuck Duplicate Primary Key Error | The transfer could not be completed because the source data contains more than one row with the same primary key value for this model. Please check the source table duplicate primary key values, deduplicate if needed, and try again. |
| PRQL-QYYA | MySQL Authentication Failed | The MySQL connection was refused due to insufficient permissions. Please check that the provided connection details have been granted sufficient access. |
| PRQL-AZBE | MySQL Connection Failed | The provided MySQL host was not found. Please check the the provided host name is valid and accessible. |
| PRQL-DQTJ | MySQL Connection Failed | The provided MySQL port is invalid. |
| PRQL-EWAS | MySQL Insufficient Create Table Permissions | The writer user does not have sufficient permissions to create tables in the destination schema. Please grant CREATE on the destination schema to the configured user and try again. |
| PRQL-VMTE | MySQL Insufficient User Permissions | One or more permissions on the database are missing from the writer user. Please ensure all required permissions are provided and retry. |
| PRQL-WCLX | MySQL Invalid Syntax Error | A SQL syntax error was encountered. Please contact support for more information. |
| PRQL-AREW | Object Storage Connection Failed | The specified bucket name contains invalid characters. |
| PRQL-EGJN | Object Storage Connection Failed | The specified bucket does not exist. |
| PRQL-SAGK | Object Storage List IO Timeout | Object Storage client encountered IO timeout listing bucket objects. If this error persists, please contact support. |
| PRQL-NQFC | Oracle Authentication Failed | The provided Oracle credentials are invalid. Please check that the correct username and password have been provided and try again. |
| PRQL-WPMU | Oracle Connection Failed | The provided Oracle port is invalid. Please check that the provided port is a valid TCP port (typically 1521). |
| PRQL-VRDH | Oracle Database Not Found | The Oracle listener at the provided host does not recognize the configured database. Please check that the provided database name is correct and try again. |
| PRQL-OXKB | Oracle Host Not Found | The provided Oracle host was not found. Please check that the provided host name is valid and accessible. |
| PRQL-CIUS | Oversized Decimal Value | Encountered a value of type DECIMAL that is too large to be converted to DECIMAL(38,19). |
| PRQL-MCOQ | Postgres Authentication Failed | The Postgres connection was refused. Please check that the provided connection details are correct. |
| PRQL-JXOS | Postgres Conflict With Recovery | The Postgres connection was dropped by the server. This is usually due to a Hot Standby related query timeout. If this error persists, please contact support. |
| PRQL-RXOI | Postgres Connection Failed | The Postgres connection was refused. Please check that the provided host is valid and accessible. |
| PRQL-TPOQ | Postgres Connection Failed | The Postgres connection was refused. Please check that the provided host is valid and accessible. |
| PRQL-VLMV | Postgres Connection Failed | The Postgres connection was refused. Please check that the provided host is valid and accessible. |
| PRQL-QJXV | Postgres Data Processing Failed | The Postgres connection encountered an error. At least one expected column was not found. |
| PRQL-SMHC | Postgres Data Processing Failed | The Postgres connection encountered an error. At least one expected relation was not found. |
| PRQL-XLSX | Postgres Data Processing Failed | The Postgres data transfer encountered duplicate primary key values. Please check that the primary key column values are unique for this recipient. |
| PRQL-FLQR | Postgres Missing PostGIS Extension | The PostGIS extenstion is required for the Postgres to recognize the type geometry. Please make sure PostGIS is installed. |
| PRQL-KKIM | Postgres Runtime Encountered Error | The Postgres connection encountered an unexpected error and was dropped. If this error persists, please contact support. |
| PRQL-KPFZ | Postgres Runtime Encountered Error | The Postgres connection was dropped by the server. If this error persists, please contact support. |
| PRQL-OKZP | Postgres Runtime Encountered Error | The Postgres connection was refused on the schema. Please check that the provided connection principal has been granted sufficient access. |
| PRQL-UKMC | Postgres Runtime Encountered Error | The Postgres connection was dropped due to a conflict with the recovery instance. This is usually due to a Hot Standby related query timeout. If this error persists, please contact support. |
| PRQL-ZSRS | Postgres Runtime Encountered Error | The Postgres connection was refused on the view. Please check that the provided connection principal has been granted sufficient access. |
| PRQL-PGST | Postgres Statement Timeout Exceeded | The query exceeded the statement_timeout configured on the Postgres database. Please raise statement_timeout for the connecting role/user: https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-STATEMENT-TIMEOUT. |
| PRQL-ROTX | Postgres cannot execute write in read-only transaction | Postgres is unable to execute the write query. Please ensure that Postgres is configured upon a writer endpoint and with write permissions. |
| PRQL-QDFS | Postgres table missing replica identity | Postgres is unable to update a destination table because it is part of a logical replication publication but has no replica identity configured. Please ensure that any published tables have a primary key, or are set to REPLICA IDENTITY FULL, or exclude them from the publication. |
| PRQL-RSLM | Record Size Limit Exceeded | One or more records in the source data exceed the maximum allowed size for import. Please reduce the size of these records or contact support for assistance. |
| PRQL-DXHS | Redshift Authentication Failed | The provided Redshift connection was refused due to insufficient permissions. Please check that the provided connection details are correct and the principal has been granted sufficient permissions. |
| PRQL-RSFA | Redshift Authentication Failed | The Redshift connection was refused. Please check that the provided connection principal has been granted sufficient access. |
| PRQL-BOWD | Redshift Authorization Failed | The provided Redshift query failed due to insufficient database permissions. Please check that the provided connection details are correct and the principal has been granted sufficient permissions to the target database. |
| PRQL-XKWZ | Redshift Cannot Drop Table with Dependencies | A DROP table operation failed due to one or more downstream consumers dependent on it. Please temporarily revoke access from downstream consumers to the destination table for the full refresh transfer to succeed. |
| PRQL-NFCL | Redshift Cluster Not Found | The specified Redshift cluster could not be found in the target region. Please check that the cluster identifier is correct and the staging bucket is located in the same AWS region as the Redshift cluster. |
| PRQL-WKQZ | Redshift Concurrent Write Conflict | A Redshift write aborted due to a conflict with a concurrent transaction on the same table. Please ensure only a single data export writer targets this schema and no other workloads are attempting to update the table. |
| PRQL-BLHI | Redshift Connection Failed | The Redshift connection was refused. Please check that the provided host is valid and accessible. |
| PRQL-FTNX | Redshift Connection Failed | The Redshift connection was refused. Please check that the provided host is valid and accessible. |
| PRQL-ZJSM | Redshift Connection Reset By Peer | The Redshift connection was reset. This is likely due to a network issue. Please check your SSH, firewall, and network settings. If the issue persists, please contact support. |
| PRQL-CSNQ | Redshift Data Processing Failed | The Redshift connection encountered an unknown error, contact support. |
| PRQL-JCVI | Redshift Data Processing Failed | The Redshift connection encountered an error. At least one expected column was not found. |
| PRQL-KMNN | Redshift Data Processing Failed | The Redshift connection encountered an error. At least one expected relation was not found. |
| PRQL-XVKM | Redshift IAM Role Token Audience Mismatch | AWS rejected the federated identity token because its audience did not match what the IAM role expects. Please verify the oaud condition in the role’s trust policy matches the provided value. |
| PRQL-WUZB | Redshift Runtime Encountered Error | The Redshift connection encountered an unexpected error and was dropped. If this error persists, please contact support. |
| PRQL-RSHA | Redshift Unable to Assume IAM Role | The Redshift connection was denied permission to assume the configured IAM role. Please verify the role’s trust policy allows sts:AssumeRoleWithWebIdentity from the service identity and try again. |
| PRQL-MWKP | S3 IAM Role Token Audience Mismatch | AWS rejected the federated identity token because its audience did not match what the IAM role expects. Please verify the oaud condition in the role’s trust policy matches the provided value. |
| PRQL-HMCK | S3 Invalid AWS Role ARN | The provided AWS IAM Role ARN is invalid. Please verify the ARN format and value is correct and try again. |
| PRQL-BKDC | S3 Invalid Hostname | The connection contains an invalid hostname. Please verify your bucket region is a valid AWS region code (e.g. eu-west-1). |
| PRQL-JSZM | S3 Missing Delete Permission | Unable to upload file to S3. Please check that the provided role has been granted s3:DeleteObject. |
| PRQL-GWUV | S3 Missing List Bucket Permission | Unable to list objects in the S3 destination bucket. Please grant the s3:ListBucket permission to the configured role on the bucket. |
| PRQL-RTTA | S3 Missing Upload Permission | Unable to upload file to S3. Please check that the provided role has been granted s3:PutObject. |
| PRQL-CIAC | S3 Tables Missing Get Table Metadata Location Permission | A query failed due to a missing s3tables:GetTableMetadataLocation permission in the user/role policy. Please check that the provided connection details are correct and the principal has been granted sufficient permissions. |
| PRQL-QLDD | S3 Tables Missing Get Table Permission | A query failed due to a missing s3tables:GetTableBucket permission in the user/role policy. Please check that the provided connection details are correct and the principal has been granted sufficient permissions. |
| PRQL-GXDD | S3 Tables Missing Update Table Metadata Location Permission | A query failed due to a missing s3tables:UpdateTableMetadataLocation permission in the user/role policy. Please check that the provided connection details are correct and the principal has been granted sufficient permissions. |
| PRQL-QGQQ | S3 Unable to Assume IAM Role | The S3 connection was denied permission to assume the configured IAM role. Please verify the custom trust policy on the role allows sts:AssumeRoleWithWebIdentity from the service identity, and that the required oaud/sub conditions are set correctly, and try again. |
| PRQL-AWJZ | SFTP Connection Lost | SFTP client experienced a connection loss. Please review any idle timeout or session limits configured on the SFTP server and retry. |
| PRQL-ANLW | SQL Server Connection Could Not Be Established | The SQL Server connection timed out. Please verify the host is reachable, firewall rules and/or security group allows access by whitelisting the static egress IP, and the port is reachable. |
| PRQL-GZDZ | SQL Server Connection Failed | The provided SQL Server host was not found. Please check that the provided host name is valid and accessible. |
| PRQL-VKDT | SQL Server Data Processing Failed | The SQL Server data transfer encountered duplicate primary key values. Please check that the primary key column values are unique for this recipient. |
| PRQL-UXPW | SQL Server Invalid Username/Password Characters | The transfer user’s username or password contains special characters that cannot be parsed during connection. Please update the user’s credentials and try again. |
| PRQL-LCNW | SQL Server Size Quota Exceeded | The database has reached its size quota. Please check the database service tier storage limit and any maximum dataset size configured, and increase allocations as needed. |
| PRQL-MURC | SQL Server unable to resolve collation conflict | A collation conflict cannot be resolved on the SQL Server table. Please contact support for more information. |
| PRQL-CLDD | Schema Not Found Error | A query failed due to a missing schema. Please check that the specified schema exists in the catalog or metastore. |
| PRQL-ZPLL | Service Temporarily Unavailable | Prequel’s import service is temporarily unavailable. Please retry shortly. If the issue persists, contact support. |
| PRQL-FKDS | Snowflake Authentication Error | Snowflake user access is disabled. Please contact the Snowflake admin to get more information. |
| PRQL-VKCP | Snowflake Authentication Failed | The Snowflake engine refused the operation due to insufficient permissions. Please check that the provided principal has been granted the required permissions. |
| PRQL-ZBSP | Snowflake Authentication Failed | The provided Snowflake credentials are invalid. Please check that the correct credentials have been provided. |
| PRQL-BJKE | Snowflake Authentication Policy Rejected | Snowflake rejected the login because the current authentication policy does not allow the attempted authentication method. Ensure the user/account policy allows DRIVERS and the chosen authentication method (PASSWORD or KEYPAIR). |
| PRQL-IGRW | Snowflake Authentication Rate Limited | The Snowflake connection was rejected. This is likely due to too many failed connection attempts. Please check that the correct credentials have been provided. |
| PRQL-EXLI | Snowflake Connection Failed | IP whitelisting has not been properly configured in the provided Snowflake account. Please contact support to confirm the correct IP address to whitelist within Snowflake. |
| PRQL-HFCO | Snowflake Connection Failed | The provided Snowflake Account Host is not valid. Please check that your provided host name is a valid Snowflake account URL (ending in ‘snowflakecomputing.com’). |
| PRQL-PKAN | Snowflake Data Processing Failed | The Snowflake connection has no active warehouse. Please ensure the provided user has a default warehouse configured. |
| PRQL-AFWL | Snowflake Database Does Not Exist or Not Authorized | The connection attempt failed due to an issue with permissions. Please confirm that the provided Snowflake database exists and the provided user has been authorized. If the error persists, please confirm that the provided user has been successfully granted access to the designated role, and that the default_role has been successfully configured on the user. |
| PRQL-NSOE | Snowflake Duplicate Row Error | The Snowflake data transfer encountered an error during data transfer. The Snowflake target table or staged data may have duplicate data preventing successful updates. Please confirm there is no duplicate data in the data source, and contact support if the issue persists. |
| PRQL-BIEM | Snowflake Host Does Not Exist | The Snowflake host was unreachable. Please ensure the host was properly entered. |
| PRQL-WLAM | Snowflake Incorrect Username or Password | The provided Snowflake username or passsword is incorrect. Please check that the correct username and password have been provided. |
| PRQL-MVKR | Snowflake Integer Overflow | A value in a Snowflake integer column exceeds the maximum supported 64-bit integer size. |
| PRQL-JWCP | Snowflake Invalid Account Setting | Failed to read the information schema due to casing. If the Snowflake account has the setting QUOTED_IDENTIFIERS_IGNORE_CASE enabled, make sure it is set to FALSE on the data transfer user. |
| PRQL-COSD | Snowflake Invalid Identifier | A Snowflake query tried to reference a table or column that does not exist. If the table or column has been deleted, it may need to be recreated manually or via full refresh. Please contact support for more information. |
| PRQL-OFWE | Snowflake Key Auth Error | The Snowflake connection was refused. Please confirm that the provided Snowflake public key has been successfully assigned to the Snowflake user. |
| PRQL-AJHJ | Snowflake Multi-factor Authentication is Required | Multi-factor authentication is currently required for the authorized user and MFA is not supported with data syncing. Please ensure your user is of type SERVICE instead of HUMAN and try again. |
| PRQL-VIED | Snowflake No Such Host Error | The Snowflake connection failed to initialize, the host provided does not exist. |
| PRQL-YWUX | Snowflake Object Verification Error | The Snowflake server was unable to verify an object. Please check that the Snowflake principal has access to the required objects. |
| PRQL-UPSD | Snowflake Password Expired | The given Snowflake password has expired. Snowflake suggests updating the password via the Snowflake web console. |
| PRQL-QZQZ | Snowflake Quota Exceeded | The designated Snowflake warehouse cannot be resumed because the warehouse’s resource monitor has exceeded its credit quota. |
| PRQL-IRPW | Snowflake Runtime Encountered Error | The Snowflake account has run out of virtual warehouse trial credit. |
| PRQL-JWOD | Snowflake Runtime Encountered Error | Snowflake reported that the statement was no longer executing (error 000605). This usually means the query was canceled before it could run, which is typically transient and resolves automatically. If the error persists, check whether the target warehouse is overloaded and scale it up if queries are queuing. |
| PRQL-WTKQ | Snowflake Runtime Encountered Error | The Snowflake account has been suspended due to the lack of a payment method. |
| PRQL-SSTE | Snowflake Session Token Expired | The Snowflake session token has expired. Please ensure the configured warehouse is active and not overloaded, and retry the transfer. |
| PRQL-SNOA | Snowflake Stage is Not Authorized | The connection encountered an issue accessing a Snowflake stage. If you have existing FUTURE STAGE grants at the database or schema level, please ensure that the transfer user’s default role is provided GRANT READ and GRANT WRITE ON FUTURE STAGES in the target schema. |
| PRQL-DSIO | Snowflake Timeout | Snowflake client encountered statement or warehouse timeout and canceled query. |
| PRQL-BKEK | Snowflake Unknown Internal Error | Snowflake returned an internal error. Review the failed query in Snowflake’s query history and check the Snowflake status page to determine whether the issue is ongoing. |
| PRQL-DICX | Snowflake Warehouse Encountered Permissions Error | The Snowflake warehouse encountered an error. Please check that the provided service account has been granted sufficient permissions. Specifically, please check for permissions on existing tables and schemas. |
| PRQL-KFSS | Source Circuit Breaker Tripped | The job encountered too many source mapping, transform, or validation errors and triggered the circuit breaker. Execution was halted early to protect system resources. Please review the failed records to determine the root cause. |
| PRQL-DCBT | Stream Circuit Breaker Tripped | Deliveries for this stream failed persistently and its circuit breaker was tripped. Loads for this stream will be skipped until the circuit breaker is reset, which you can do by updating the stream once the underlying failure is addressed. |
| PRQL-ANCT | Transfer Dispatch Error | The transfer failed to be dispatched to a worker. |
| PRQL-IDWD | Trino Exceeded Partitions Limit | The Trino engine encountered an error because too many partitions were found. |
| PRQL-ERMS | Unknown Error | An unknown error occurred. |
| PRQL-XFVC | Unsupported Table Type | The specified table type is not supported for this datalake operation. |