AI incidents: ChatGPT scheduled-write failures and Ads onboarding blocks — 19 October 2026

Publisher disclosure: MUVO offers competing music, remix, and video tools. This report summarizes public sources and provider documentation; it is not an independent product test or a claim that MUVO is free of similar issues. Read our reporting method.

Incident summary and status at publication

Today’s findings concern two specific OpenAI workflows: scheduled connected-app writes and advertiser onboarding. The research window runs from 16 October at 11:53 to 19 October at 11:55 Europe/Istanbul (UTC+3). Neither finding establishes a platform-wide outage or a new incident starting today.

ChatGPT Scheduled Tasks: blocked writes, with successful counterexamples

Independent accounts on 18–19 October describe scheduled SharePoint copies and GitHub, Notion and custom-MCP writes being rejected by safety checks. The SharePoint reporter says the equivalent interactive copy succeeded; scheduled folder creation and Outlook calendar actions also worked. These are user observations, not MUVO tests. SharePoint account, GitHub, Notion and MCP account.

On 16 October at 23:22 Istanbul, OpenAI Support said traced Gmail sends encountered a safety check before app permissions applied; Sheets succeeded in one run and was blocked in another. That acknowledgement does not establish a shared cause for every connector report. Support findings.

Practical next step: Support suggests trying Work where available, first pausing the original task and checking existing changes to avoid duplicates. Work has a different approval flow and may still require confirmation. This is a suggested workaround, not a confirmed fix. Provider guidance.

ChatGPT Ads: staff acknowledge the business-icon onboarding problem

An OpenAI staff reply on 19 October at 07:54 Istanbul calls the reported Ads onboarding problem known and says a fix is forthcoming. It gives no release time or confirmation of recovery. Staff response.

The original 12 October account describes an advertiser unable to save a required business icon. The reporter says image upload succeeded, but saving account metadata returned a verification-related error. Other users subsequently reported the same onboarding obstacle. This concerns creating ads, not ordinary ChatGPT conversations or AI image generation. Original account and technical observations, Follow-up account.

Practical next step: Staff ask affected advertisers with an existing support ticket to continue there. The thread does not establish an account-wide workaround, affected regions or a universal verification defect. User debugging is not an official root-cause finding. Support direction.

Evidence limits and earlier coverage

These sources do not establish reliable impact start/end pairs, affected-user totals or a general recovery. We therefore give post times, not outage durations. Public community accounts are not necessarily verified customer reviews.

We also rechecked music, video and remix tools, major-provider histories and the issues in our 18 October incident edition. Repeated complaints without a material new finding do not create another incident. Inaccessible sources remain coverage gaps, not evidence that a service is healthy.

The release scan did not establish enough material new product information for a separate news edition today. The latest product-news edition retains its original date. Read our reporting method.

Sources

• Scheduled writes: 18 October firsthand account, 19 October independent account, 16 October OpenAI Support response.
• Ads onboarding: original report, 18 October follow-up, 19 October staff acknowledgement.
• Official incident-history cross-checks: OpenAI, Anthropic and ElevenLabs. These histories do not establish the scope of the community reports above.

Update timeline

• 19 October 2026, 11:55 Istanbul: Research cutoff for this edition. Added the scheduled-write evidence and Ads staff response. Earlier articles remain unchanged; publication time is separate from the reported events.