GitHub connector: fetch_workflow_job_logs returns no log content for some valid Actions jobs

What issue are you seeing?

The ChatGPT GitHub connector exposes fetch_workflow_job_logs(repo_full_name, job_id) for retrieving decoded GitHub Actions job logs. The tool still works for some jobs, but for at least one valid Actions job it returns no usable log content even though the same connector can successfully retrieve the workflow run, job metadata, and job steps.

This appears to be isolated to the job-log download / temporary redirect / decoding path rather than repository authentication or general Actions access.

The behavior changed recently: I successfully used the same connector to retrieve and inspect full Actions job logs on August 24, 2026, and again on the morning of August 25, 2026. The failure has been reproduced repeatedly later on August 25.

Reproduction

Failing case:

repo: sanshan/event-driven-platform
run_id: 32821202581
job_id: 97719508021
job name: Affected validation
job conclusion: failure

For this job:

fetch_workflow_run_jobs(repo_full_name, run_id)  -> works
fetch_workflow_job_steps(repo_full_name, job_id) -> works
fetch_workflow_job_logs(repo_full_name, job_id)  -> no usable decoded log content

The job metadata is accessible and shows that step 13 failed:

Verify packages through Verdaccio with Redis read composition

However, the actual stdout/stderr log body cannot be retrieved through fetch_workflow_job_logs.

Control case, tested in the same connector/session:

repo: sanshan/accounterbro
run_id: 32786856743
job_id: 97620437513
job name: Test and build
job conclusion: success

For this job:

fetch_workflow_job_logs(repo_full_name, job_id) -> full decoded Actions log

So the tool is not globally unavailable. The same account, connector, and session can retrieve full logs for one Actions job while failing to surface log content for another.

Expected behavior

fetch_workflow_job_logs should return the decoded GitHub Actions job log for any accessible job whose logs are available from GitHub.

If GitHub's temporary log URL cannot be downloaded or decoded, the connector should return an explicit error describing the failed stage rather than an empty/unusable result.

Actual behavior

For job 97719508021, the connector can read the workflow run and job steps but repeated fetch_workflow_job_logs calls do not surface the decoded log body.

For control job 97620437513, the same method successfully returns thousands of lines of decoded log text.

Why this looks connector-specific

GitHub's REST endpoint for downloading job logs uses a temporary redirect. The connector's tool description explicitly states that the underlying client follows that redirect before decoding the bytes.

The A/B result suggests a job-specific or intermittent failure in that redirect/download/decoding path rather than a missing permission:

• repository access works;
• workflow run access works;
• job metadata access works;
• job step access works;
• job-log retrieval works for another repository/job in the same session.

Environment

• Product surface: ChatGPT native iOS app
• Subscription: ChatGPT Plus
• Date reproduced: August 25, 2026
• GitHub connector: connected and otherwise functional

Additional information

This is not a request to add GitHub Actions log support: the connector already exposes fetch_workflow_job_logs, and the method successfully returned full log text for other jobs shortly before and during the same troubleshooting session.

I searched the current openai/codex issue tracker for fetch_workflow_job_logs, workflow job logs, and GitHub connector log failures and did not find an exact duplicate.

If useful, I can provide additional public job IDs from the same repository to determine whether the failure correlates with failed jobs, workflow type, log size, or a particular run.