Hmm, I don't know enough to give you a confident answer yet. However, I recommend checking the [Airbyte documentation](https://docs.airbyte.com) and [Airbyte forum](https://discuss.airbyte.io) for similar issues and potential solutions. If you still face issues, consider sharing the full sync log for more insights.
05/25/2023, 7:30 PM
@kapa.ai 2023-05-24 19:55:56 ^[[43mdestination^[[0m > INFO i.a.i.b.FailureTrackingAirbyteMessageConsumer(close):80 Airbyte message consumer: succeeded.
2023-05-24 19:55:56 ^[[43mdestination^[[0m > INFO i.a.i.d.b.BufferedStreamConsumer(close):257 executing on success close procedure.
Based on the provided extracts, it's not clear why the "on success close procedure" is being executed in your specific case. However, it's important to note that the "on success close procedure" is a normal part of the Airbyte data processing flow. It indicates that the data processing has been successful, and the connection is being closed as part of the cleanup process. If you're experiencing any issues or need more information about Airbyte connectors or the Airbyte protocol, you can refer to the [Airbyte documentation](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol).