airbyte connection failed because of some transient dns issue . on the second attempt for job , it tries to rerun discovery. this is a problem because the start date on the connector is older than we can get data for. is there a way to get airbyte to not rerun discovery on a failed job attempt?

I'm sorry, but the knowledge sources do not contain explicit information about configuring Airbyte to skip the discovery phase on retry attempts after a failed job. The available documentation describes Airbyte's retry logic and backoff strategies for failed sync jobs, but does not mention an option to prevent discovery from running again on retries or how to handle cases where the connector's start date is no longer valid for data extraction after a transient failure like a DNS issue. If this behavior is causing issues in your workflow, you may want to open a feature request or issue on the Airbyte GitHub repository to discuss this use case with the Airbyte team and community.