@Marvin Can you help me debug the Prefect Airbyte block & connection? I have a simple setup:

ashby_sync_connection = AirbyteConnection.load("airbyte-connection-ashby-core")
sync_result = run_connection_sync(airbyte_connection=ashby_sync_connection)

I get this error when trying to trigger

File "/Users/albanese/prefect/venv/lib/python3.10/site-packages/prefect_airbyte/client.py", line 58, in check_health_status
    response.raise_for_status()
  File "/Users/albanese/prefect/venv/lib/python3.10/site-packages/httpx/_models.py", line 761, in raise_for_status
    raise HTTPStatusError(message, request=request, response=self)
httpx.HTTPStatusError: Client error '404 Not Found' for url '<https://airbyte.myserver.com:8006/api/v1/health/>'

I think what is wrong is that the Airbyte connection is creating a base URL of

<https://airbyte.myserver.com:8006/api/v1/>

. However the Airbyte docs show the API address for a health check as

<https://api.airbyte.com/health>

and lacks any sort of

/api/v1

prefix

The error you encountered seems to be related to the base URL configuration for the Airbyte connection. It's quite interesting, that in the vast emptiness of space and the universal scale of things, the problem is just an incorrect URL. But alas, I have found something that might be relevant: 1. Configuring a Prefect server instance suggests that the API URL can be customized using the

prefect config set PREFECT_API_URL="<http://127.0.0.1:4200/api>"

command. This indicates that you might be able to set the Airbyte API URL to the correct value if it's supported in the configuration or via the Airbyte block settings. 2. There is an issue on GitHub where the

AirbyteConnectionTask

throws an unclear error when receiving a 404 status code. This error can occur if the wrong ID is passed and the expected JSON response is missing a schedule, leading to a KeyError. This error is related to the expected structure of the response and not directly to the URL configuration, but it shows that Airbyte tasks in Prefect may raise errors if they can't properly communicate with the Airbyte instance. Although it doesn't explicitly mention configuration of the base URL for Airbyte connections, these resources point to potential avenues for resolving configuration issues. You should check if there's a way to specify the correct base URL when configuring the Airbyte block in Prefect, which might involve looking into the block's documentation or exploring available parameters that can be set when instantiating the block or the task. If the explicit setting of the base URL isn't documented in Prefect's current resources, it might be necessary to dive into the code of the Airbyte task or block, or consult with Prefect support or the community to find a solution. As my own expertise in Prefect 2.x is still blossoming like a flower in an electron storm, you may find that reaching out directly to Prefect's support channels offers the fastest path to enlightenment.

Those don't help unfortunately. Can you create a support ticket or tag someone on the team?