@kapa.ai I have an issue with my connection. It tries to pull the airbyte/source-declarative-manifest:0.78.1 but does not success.

Based on the information provided in the knowledge sources, it appears you're experiencing an issue related to pulling the Docker image for the declarative manifest source connector. This is a known issue that has been reported by other users. Here's what we know and some potential solutions: 1. Image Availability: First, ensure that the image

airbyte/source-declarative-manifest:0.78.1

actually exists. You can check its availability on [Docker Hub](https://hub.docker.com/r/airbyte/source-declarative-manifest/tags). 2. Manual Pull: Try pulling the image manually using Docker to see if it's a general issue or specific to Airbyte:

docker pull airbyte/source-declarative-manifest:0.78.1

If this succeeds, it suggests the image is available and the issue might be with Airbyte's pulling mechanism [GitHub Issue #39424](https://github.com/airbytehq/airbyte/issues/39424). 3. Version Mismatch: There might be a version mismatch between the manifest version and the airbyte-cdk package version. This can cause issues as reported in [GitHub Issue #45398](https://github.com/airbytehq/airbyte/issues/45398). 4. Workaround: If you're using a Helm chart, you might need to update the docker image tag in your database. A user suggested this workaround:

SQL    UPDATE "public"."actor_definition_version"    SET docker_image_tag='4.6.2'    WHERE id = '<ID_RETRIEVED>';

However, note that this workaround might not be permanent and could reset after an Airbyte pod restart [GitHub Issue #45398](https://github.com/airbytehq/airbyte/issues/45398). 5. Check for Rate Limiting: If you're pulling a large amount of data, you might be experiencing rate limiting. Airbyte will display an informational message if this is the case [Airbyte Docs](https://docs.airbyte.com/cloud/managing-airbyte-cloud/review-connection-status#connection-troubleshooting). 6. System Restart: Some users have reported that restarting Docker or the entire Airbyte system resolved the issue temporarily [GitHub Issue #39424](https://github.com/airbytehq/airbyte/issues/39424). If none of these solutions work, you might want to check for any recent updates to Airbyte or consider upgrading to the latest version if you're not already using it. The issue might have been resolved in a newer release.