@kapa.ai: jobHistory.logs.logDownloadFailed when downloading the logs from Airbyte UI

The knowledge sources mention that sometimes the “Download logs” buttons in the Airbyte UI appear non‑functional or fail, but they do not document a specific

jobHistory.logs.logDownloadFailed

error string or a precise root cause. So the guidance below is based only on what is explicitly available. From the docs and forum threads: 1. How log download is supposed to work - For a given connection, go to the Job History tab, open the menu (three dots) next to a sync, and choose Download logs. This should download a local file containing all attempts’ logs for that job. [[Browsing logs](https://docs.airbyte.com/platform/operator-guides/browsing-output-logs); [Logs 1.8](https://docs.airbyte.com/platform/1.8/operator-guides/browsing-output-logs)] 2. Known UI issues / troubleshooting steps - There are reports that the Download Server Logs / Download Scheduler Logs buttons in the UI sometimes do nothing, even though the underlying HTTP request completes. [[Forum 717](https://discuss.airbyte.io/t/717); [Forum 848](https://discuss.airbyte.io/t/848)] - In those cases, support recommends: - Open your browser Developer Tools → Network tab. - Click the log download button again. - Inspect the failing request’s response to see if there is an error message or HTTP status code. [[Forum 717](https://discuss.airbyte.io/t/717); [Forum 5428](https://discuss.airbyte.io/t/5428)] 3. What you can do now Since the sources don’t describe

jobHistory.logs.logDownloadFailed

specifically, the best supported steps are: 1. In the Airbyte UI, reproduce the error while Network tab is open. 2. Check: - Request URL and method. - Response status (e.g. 4xx/5xx). - Response body for any error text. 3. If the network request succeeds but the file doesn’t appear, it matches the known “button does nothing” behavior; in that case, you may need to: - Download logs directly from your deployment (e.g., Kubernetes pod logs or Docker volumes) as a workaround. [[Browsing logs](https://docs.airbyte.com/platform/operator-guides/browsing-output-logs); [Forum 717](https://discuss.airbyte.io/t/717)] 4. If you open a community post or ticket, include: - The failing request’s URL, status code, and response body. - Your Airbyte version and deployment type (Docker/Kubernetes/etc.). [[Forum 717](https://discuss.airbyte.io/t/717)] Because the documentation and forum posts do not mention

jobHistory.logs.logDownloadFailed

by name, I can’t give a more precise cause or fix from these sources alone. If you can share the HTTP status and response body from the failing download request, that would be the next concrete step.