Nick Prestemon
10/25/2023, 3:10 PMkapa.ai
10/25/2023, 3:11 PMdocker logs command to view the logs of the specific container that's causing the issue. If the error messages in the logs are not clear, you can use the AirbyteTraceMessageUtility class provided by Airbyte to emit more user-friendly error messages. Here's an example of how to use it: java try { // some connector code responsible for doing X } catch (ExceptionIndicatingIncorrectCredentials credErr) { AirbyteTraceMessageUtility.emitConfigErrorTrace( credErr, "Connector failed due to incorrect credentials while doing X. Please check your connection is using valid credentials.") throw credErr } catch (ExceptionIndicatingKnownErrorY knownErr) { AirbyteTraceMessageUtility.emitSystemErrorTrace( knownErr, "Connector failed because of reason Y while doing X. Please check/do/make ... to resolve this.") throw knownErr } catch (Exception e) { AirbyteTraceMessageUtility.emitSystemErrorTrace( e, "Connector failed while doing X. Possible reasons for this could be ...") throw e } (Source: [Building a Java Destination](https://docs.airbyte.com/connector-development/tutorials/building-a-java-destination)) If you're still having trouble figuring out the error, you can reach out to the Airbyte community on the [Airbyte Forum](https://github.com/airbytehq/airbyte/discussions) or open a support ticket through the [Airbyte Cloud platform](https://docs.airbyte.com/operator-guides/contact-support) or [Help Center](https://support.airbyte.com/hc/en-us).Nick Prestemon
10/25/2023, 3:12 PMkapa.ai
10/25/2023, 3:15 PM