Hey guys! Great job with the API development! We currently using shipyardapp.com to orchestrate our data pipelines, so we are integrating Airbyte API, we are having some troubles checking the status of the job, according the blueprint documentation in shipyard (https://www.shipyardapp.com/docs/blueprint-library/airbyte/Airbyte-authorization/) the API should return something like this

{
  "jobId": 1234,
  "status": "running",
  "jobType": "sync"
}

But we are getting a different response, something like this

Changing working directory to /home/shipyard

Setting environment variable AIRBYTE_CONNECTION_ID=[XXXX]
Setting environment variable AIRBYTE_API_TOKEN=[XXX]
Downloading file trigger_syc.py ...

2023-05-11 17:04:31,510 - Shipyard - INFO - Airbyte sync successfully triggered

Any thought on that? Thanks!

A message from kapa.ai

Hmm, I don't know enough to give you a confident answer yet. The information extracts provided don't cover the specific issue you're facing with Shipyard integration. However, you can refer to the [Airbyte API documentation](https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html) for more details on how to work with the Airbyte API and job statuses.

Hey @Jesus Sosa 👋 I'm not too familiar with Shipyard "under-the-hood" @Wesley Poulsen Is this expected behaviour from the Shipyard application?

Hi @Jesus Sosa. This is expected behavior in Shipyard. We don’t print out the response from the Airbyte API but instead provide a different message to stdout. If you would like to check the status of your Airbyte Sync, you can use the

Airbyte - Check Sync Status

blueprint that we have. This is best used immediately after the

Airbyte - Trigger Sync

blueprint

Hi @Wesley Poulsen actually I'm using both blueprints connected in the same pipeline, but seems like the

Airbyte - Check Sync Status

is not getting the

job-id

so it's finishing in seconds and not checking the status as should be.

Can you send me what the logs for that check status vessel are?

Hey @Wesley Poulsen here I send you the logs for

Trigger Sync

Changing working directory to /home/shipyard

Setting environment variable AIRBYTE_CONNECTION_ID=[XXXXX]
Setting environment variable AIRBYTE_API_TOKEN=[XXX]
Downloading file trigger_syc.py ...

2023-05-11 18:32:06,686 - Shipyard - INFO - Airbyte sync successfully triggered

And for the

Job Status

Changing working directory to /home/shipyard

Setting environment variable AIRBYTE_API_TOKEN=[XXX]
Setting environment variable AIRBYTE_JOB_ID=
Downloading file check_status.py ...

Thanks!

There was a small bug here that has been fixed now. The check status should work for you now, though you may need to configure how many times you would like it to retry in the guardrails section. Can you check and see if it works fine on your side now?

I did the adjustments and did work as expected. Thank you guys! Awesome job!