@kapa.ai getting this error:

'No streams are available for source SourceGoogleDrive. This is probably an issue with the connector. Please verify that your configuration provides permissions to list and read files from the source. Contact support if you are unable to resolve this issue.'

here are the logs:

2025-12-16 17:41:38 info 
2025-12-16 17:41:38 info ----- START CHECK -----
2025-12-16 17:41:38 info 
2025-12-16 17:41:39 info Connector exited, processing output
2025-12-16 17:41:39 info Output file jobOutput.json found
2025-12-16 17:41:39 info Connector exited with exit code 0
2025-12-16 17:41:39 info Reading messages from protocol version 0.2.0
2025-12-16 17:41:40 error Check failed
2025-12-16 17:41:40 info Checking for optional control message...
2025-12-16 17:41:40 info Optional control message not found. Skipping...
2025-12-16 17:41:40 info Writing output of 9f8dda77-1048-4368-815b-269bf54ee9b8_8696ae51-776d-4692-91d0-30b36a486cb3_0_check to the doc store
2025-12-16 17:41:40 info Marking workload 9f8dda77-1048-4368-815b-269bf54ee9b8_8696ae51-776d-4692-91d0-30b36a486cb3_0_check as successful
2025-12-16 17:41:40 info Deliberately exiting process with code 0.
2025-12-16 17:41:40 info 
2025-12-16 17:41:40 info ----- END CHECK -----
2025-12-16 17:41:40 info

what is this telling me?

The knowledge sources don’t describe this exact error text for

SourceGoogleDrive

, but they do show the same pattern of a failing check: connector exits with code 0, Airbyte reads

jobOutput.json

, then logs

Check failed

and a user-facing message about listing/reading files. [[Check & error handling](https://docs.airbyte.com/platform/connector-development/tutorials/custom-python-connector/check-and-error-handling)] What your logs mean: - The connector container ran successfully (exit code 0,

jobOutput.json found

). - Inside that run, the connection check failed: Airbyte’s worker parsed the connector’s output and determined that no usable streams were available, so it surfaced the error: > No streams are available for source SourceGoogleDrive. This is probably an issue with the connector. Please verify that your configuration provides permissions to list and read files from the source. For Google Drive specifically, this usually indicates one of: 1. The connector could not list files in the configured folder with the provided credentials (permissions / scopes / sharing). [[Google Drive source](https://docs.airbyte.com/integrations/sources/google-drive)] 2. There are effectively no files discoverable under the folder path the connector is pointed at (or the folder link is wrong). [[Google Drive source](https://docs.airbyte.com/integrations/sources/google-drive)] Given the docs, here’s what to double‑check in your setup: [[Google Drive source](https://docs.airbyte.com/integrations/sources/google-drive)] 1. Folder link - Ensure the “Drive folder link” in the source config is exactly the folder you want to sync (not a file link, not a parent you don’t have access to). 2. Authentication type & permissions - If using Service Account (recommended for OSS): - The Google Drive API is enabled on the GCP project. - The service account email has at least Viewer access to that folder (share the folder with the service account if needed). - If using OAuth: - The app has the

<https://www.googleapis.com/auth/drive.readonly>

scope. - The authenticated user can open that folder and see files in the UI. 3. That there are actually files - Confirm there is at least one file in that folder (or subfolders) that the authenticated identity can see. If you’ve confirmed all of the above and still get “No streams are available,” the message is likely pointing to a connector-side issue (similar to other “Check failed” patterns in the issues), and you may need to open a GitHub issue with your connector version and redacted logs so the team can investigate.