@kapa.ai how can I set the timeout for an initial test of a newly created connector?

The timeout for an initial test of a newly created connector is not directly configurable. However, there are certain parameters that can influence the timeout behavior. For example, in the case of Postgres and MySQL connectors, the initial CDC waiting time can be set. The connector waits for the default initial wait time of 5 minutes (300 seconds). Setting the parameter to a longer duration will result in slower syncs, while setting it to a shorter duration may cause the connector to not have enough time to create the initial snapshot or read through the change logs. The valid range is 120 seconds to 1200 seconds for Postgres and 300 seconds to 1200 seconds for MySQL. If the connector cannot read the database changes, you can increase the waiting time to test if insufficient waiting time is the root cause ([source for Postgres](https://docs.airbyte.com/integrations/sources/postgres/postgres-troubleshooting#advanced-setting-up-initial-cdc-waiting-time), [source for MySQL](https://docs.airbyte.com/integrations/sources/mysql/mysql-troubleshooting#advanced-setting-up-initial-cdc-waiting-time)). For Vertica destination, the connector supports

connectTimeout

and defaults to 60 seconds. Setting connectTimeout to 0 seconds will set the timeout to the longest time available ([source](https://docs.airbyte.com/integrations/destinations/vertica#naming-conventions)). In the case of a database source connector with hundreds to thousands of tables, each with many columns, the one-time

discover

mechanism may run for a long time and exceed Airbyte's timeout duration. In this case, you can increase Airbyte's timeout limit as follows:

yaml server:     extraEnvs:       - name: HTTP_IDLE_TIMEOUT         value: 20m       - name: READ_TIMEOUT         value: 30m

([source](https://docs.airbyte.com/enterprise-setup/scaling-airbyte#schema-discovery-timeouts)) Please note that these settings are specific to certain connectors and may not apply to all connectors. Always refer to the specific documentation for the connector you are using.

Is there a timeout configurable for the redshift connector?