Google Sheets connection

Ask the Community
1

I have created a google sheets connection and I can see the data. When I try to create a sync it fails with the following message: Unexpected infrastructure failure: the job has failed unexpectedly in the backing compute cluster without committing or aborting. Reason: Job failed with the following container states:

Any one seen this issue if so how do you correct it.

2

The error message, “the job has failed unexpectedly in the backing compute cluster without committing or aborting,” indicates an infrastructure-level issue in the compute environment running the sync. While there is no documented root cause for this specific error, a few common areas are worth checking before escalating to support.

1. Verify Network Connectivity and Egress Settings

The Google Sheets connector requires access to the following Google domains:

  • accounts.google.com (OAuth authentication)
  • www.googleapis.com (Google API access)

If outbound network access is restricted and these domains are not allowlisted, sync jobs may fail before completing successfully.

What to check:

  • Open the Google Sheets data source configuration.
  • Review the networking or egress settings.
  • Confirm that both required Google domains are permitted.
  • Check with your platform administrator if outbound network policies are managed centrally.

2. Refresh Authentication

If data exploration works but synchronization fails, authentication credentials may have expired or may not be valid for the sync process.

Recommended steps:

  • Open the Google Sheets source configuration.
  • Reauthenticate or refresh the OAuth credentials.
  • Save the configuration and run the sync again.

3. Contact Support if the Issue Persists

The container-state error typically requires access to backend logs that are not available to end users. When opening a support case, include:

  • Data source name and identifier
  • Timestamp of the failed sync
  • Complete error message
  • Confirmation that data exploration works successfully
  • Whether the sync has worked previously or this is the first attempt

If the issue is related to the underlying compute environment, the support team will be able to investigate the backend logs and identify the root cause.

3

I did try ask those things first but it did not work. I saw some information about the container failing because of memory issues. The sheet only has 50 rows of data so I don’t think it’s a memory issue