Hello, why does post /v1/sources/check_connection ...
# replication-ask-ai
j
Hello, why does post /v1/sources/check_connection return a jobId: uuid, while other job ids are integers? I'm trying to monitor the status of the check connection call but can't call post/v1/jobs/get with a uuid value.
Under the job schema it shows the accepted config types so I don't understand why I can't get the job id for check_connection_source. configType*: enum Allowed: check_connection_source┃check_connection_destination┃discover_schema┃ge
j
Hey James, there are two types of jobs: synchronous jobs (e.g. the source CHECK command you’re executing with
/v1/sources/check_connection
) and asynchronous/long-running jobs (e.g. data syncs). The former uses a
uuid
id and the latter uses an
int
id. You can read more about the job architecture in the docs here. You can’t use the
post/v1/jobs/get
endpoint to get info about a synchronous job, only an async job. Synchronous jobs should execute quickly (synchronously 🙂) and should generally not need monitoring.
j
Thanks @Joey Marshment-Howell (Airbyte), the reason I'm asking is because one of my sources can take up to 5 minutes to respond when check_connection_source is called. I was looking for a way to monitor this job within the 30 second AWS timeout window.