Troubleshoot input table connection issues

When you encounter an input table error (as a general user) or receive a system email notifying you of failed input table edits (as an admin), it can be the result of a configuration or availability issue in your connection or data platform. This type of issue must be resolved by an admin within Sigma or directly in the data platform.

This document explains how Sigma handles input table errors resulting from configuration and availability issues and provides guidance on troubleshooting and resolving these errors.

User requirements

The ability to resolve an input table issue identified in this document requires the following:

• You must be assigned the Admin account type.

• You must have the necessary privileges in the data platform to perform the resolution tasks identified in this document.

If you don't meet these requirements, contact your Sigma or data platform administrator to resolve the issue.

Input table error handling

To improve data integrity and prevent unexpected data loss, Sigma handles input table errors as follows:

• When an input table edit is unsuccessful due to configuration or availability issues in the connection or data platform, Sigma treats it as a fatal error and does not retry the operation. The underlying issue is not recoverable by Sigma, therefore, retrying the operation would continue to fail.

• An input table error resulting from a configuration or availability issue in the connection or data platform can apply to specific users or the entire organization. When Sigma detects this type of issue, it temporarily restricts the ability for affected users to create and edit input tables that are subject to the same error. Following the initial input table error, all relevant existing input table elements display an “Editing restricted” message.

• Sigma sends admins an email alert that identifies the misconfigured or unavailable connection, displays the error message, and links to this document.

Troubleshooting steps

Complete the following steps to troubleshoot the error.

1. Review the organization and connection identified in the system email. This is important if you manage multiple organizations or connections.

2. Check the error message identified in the system email.

3. Locate the error message in the Error messages and resolutions tables. If you cannot find the applicable error message, contact Support.

4. Review the root cause, then complete the resolution provided for the authentication method configured on your connection.

Error messages and resolutions

This section provides details about known configuration and availability errors specific to BigQuery, Databricks, PostgreSQL, Redshift, and Snowflake. If you encounter an error message that's not included in the following tables, contact Support.

CREATE TABLE IF NOT EXISTS <project>.<dataset>.SIGDS_WAL_<connection_id> (
  DS_ID BYTES NOT NULL,
  EDIT_ID BYTES NOT NULL,
  USER_ID BYTES NOT NULL,
  EDIT_NUM INT64 NOT NULL,
  PROTOCOL_VERSION INT64 NOT NULL,
  EDIT JSON NOT NULL,
  METADATA STRING NOT NULL,
  TIMESTAMP TIMESTAMP NOT NULL
)