Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Aloja :wave:

Getting a constant stream of this error
```"query directly through matching on sticky timed out, attempting to query on non-sticky```
when running airbyte locally (docker). It makes reading logs basically impossible and it does not seem to affect functionality. Any clues? It seems to be related to <https://www.google.com/search?q=query+directly+through+matching+on+sticky+timed+out%2C+attempting+to+query+on+non-sticky&amp;sourceid=chrome&amp;ie=UTF-8|Temporal>.

Here's the full log:

```{"level":"info","ts":"2022-11-08T15:19:46.190Z","msg":"query directly through matching on sticky timed out, attempting to query on non-sticky","service":"history","shard-id":1,"address":"172.19.0.8:7234","shard-item":"0x4000797300","component":"history-engine","wf-namespace":"default","wf-id":"connection_manager_9387d5d6-c538-4f89-8fce-d25833af8d12","wf-run-id":"3af4caf5-033a-49d8-9c74-bdbf6e2c9d6b","wf-query-type":"getState","wf-task-queue-name":"","wf-next-event-id":33,"logging-call-at":"historyEngine.go:923"}```

Hi, Gerard! Could you please give me a few more details - your Airbyte and connector versions and where your Airbyte instance is deployed. Thanks!

This is in local development (docker) and with latest pull from master branch

Are you able to access the UI and run any syncs? I've found an issue that's partially relevant, so trying to narrow down the other factors -
<https://github.com/airbytehq/airbyte/issues/14289>

My use case is a bit particular since I'm doing everything via the API, and for that what I'm doing is calling the <https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html#post-/v1/connections/create|create connection> api endpoint with the payload I get when calling the <https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html#post-/v1/sources/discover_schema|discover schema> endpoint (this is from a postgres source to a clickhouse destination)

I think it might be related to some misconfigured connection/source/destination

Oh thanks for the details! I'm wondering if somehow the JSON schemas you're getting from the `discover_schema` endpoint weren't valid. It's bizarre that everything's working if that's the case, but could be a possibility.

Could you check the schema from that endpoint using this validator?
<https://www.jsonschemavalidator.net/>

I think it was a previous conection I created with an incomplete schema

resetting the local state the error has disappeared so no more worries for now

quick question, what happens if I request a manual sync and another sync is already in progress for the same connection?

Do the syncs run in parallel? They get queued? They get ignored?

So glad it got resolved! I am not sure what would happen, I think that's undocumented as of now. I know that syncs cannot run in parallel like that, so my guess would be that they either get queued, or one gets ignored. If you try this out, please let me know :slightly_smiling_face: I'd be curious to find out!