#Scheduled Tasks fail to use connected app tools while the same tools work in Chat and Work

3 messages · Page 1 of 1 (latest)

hasty masonBOT
#

Reported by @vestal whale

Bug Report: Scheduled Tasks fail to use connected app tools while the same tools work in Chat and Work
`Steps to Reproduce`
  1. Connect Google Drive/Sheets to ChatGPT.
  2. In a normal Chat or Work session, read and update a connected file successfully.
  3. Create a Scheduled Task that performs the same connected-app action.
  4. Let the task run automatically in the background.
  5. The Scheduled Task fails, blocks the tool call, or cannot complete the action, while the identical action still works interactively.
`Expected Result`

Scheduled Tasks should be able to use authorized connected-app tools with the same account permissions available to Chat/Work. If the connection and permissions are valid, a background Scheduled Task should be able to complete the authorized action without requiring an approval that cannot be answered during unattended execution.

`Actual Result`

The same connected apps and files work normally in interactive Chat/Work, but Scheduled Tasks fail when running in the background. The failure is reproducible with the same account, connection, and target files. This appears isolated to the Scheduled/background execution environment rather than the connected app itself. In some runs, tool execution is blocked or cannot proceed through the approval/permission path.

`Environment`

ChatGPT Scheduled Tasks / background execution Same ChatGPT account and same connected apps used for A/B testing Google Drive / Google Sheets connected Interactive Chat and Work: working Scheduled/background execution: failing Issue observed around September 24–25, 2026 Client used to inspect/manage tasks: ChatGPT iOS app and web

#
Additional Information

Please provide relevant details to help resolve the issue, such as:

  • ChatGPT Shared Link (if applicable).
  • Screenshots or videos demonstrating the problem.

-# ➜ Need to contact support? Visit the OpenAI Help Center.

vestal whale
#

This is reproducible as an A/B test. No account, OAuth connection, file permission, or target document is changed between tests. The connected-app action succeeds when initiated from an interactive Chat/Work session, but fails when the same type of action is executed by a Scheduled Task in the background.

Multiple scheduled agents/workflows were affected at approximately the same time. Reconnecting or changing the target file does not explain the behavior because interactive access continues to work.

The behavior suggests a problem in the Scheduled Task execution context, tool routing, or approval/permission handling for connected apps. I am not claiming a specific root cause, but the failure appears specific to unattended Scheduled execution.

Please compare the permission/tool-call context used by interactive Chat/Work with the context used by Scheduled Task runs.