Hayden Ness
05/27/2024, 3:53 AMkapa.ai
05/27/2024, 3:53 AMworker pod and up to 1G in RAM & 1 CPU for temporal and webapp pods) but still faced issues. [Source](https://github.com/airbytehq/airbyte/issues/31695). 3. Timeout Issues: There have been instances where users faced timeout errors when connecting to SQL Server. This could be related to the Hikari connection pool timing out. Ensure that your network settings and SQL Server configurations are optimized to handle large schema fetches. [Source](https://github.com/airbytehq/airbyte/discussions/31267). 4. Version Compatibility: Ensure that you are using a compatible version of Airbyte. There have been reports of errors occurring after upgrading to certain versions. If you recently upgraded, consider rolling back to a previous stable version to see if the issue persists. [Source](https://github.com/airbytehq/airbyte/issues/27837). 5. Logs and Debugging: Check the logs for any specific error messages that might give more insight into the issue. If there are no logs in the worker pod, it might indicate a deeper issue with the deployment or configuration. If these steps do not resolve the issue, you might want to provide more details on the specific error messages and your current setup for further assistance. You can also refer to the [Airbyte documentation](https://docs.airbyte.com/) for more detailed troubleshooting steps. If you need further assistance, you can also raise an issue on the [Airbyte GitHub repository](https://github.com/airbytehq/airbyte/issues) or seek help on the [Airbyte community forum](https://discuss.airbyte.io/).