Project Sources fail to save new responses in large Projects

Environment

  • Surface: ChatGPT native iOS app
  • Device: iPhone 17 Pro Max
  • Subscription: ChatGPT Plus
  • Current app version: 1.2026.300
  • Affected feature: Projects → Add to project sources
  • Other platforms: I’ve also experienced difficulties using Project Sources in the native macOS app, although I haven’t established whether it’s the same underlying issue.
  • First documented incident: 27 August 2026, on an earlier iOS app version.

Bug

I’m a heavy ChatGPT Projects user, particularly for D&D campaigns, creative writing and long-running conversations where maintaining continuity is extremely important.

I’ve encountered a recurring problem where large Projects sometimes refuse to accept additional saved assistant responses.

In one Project, I manually counted 101 individual saved-response entries under Project Sources. When I attempted to add further responses, ChatGPT repeatedly displayed:

“Couldn’t update project sources. Please try again.”

However, I discovered something interesting during troubleshooting.

I tried saving a response in another Project using the same iPhone, account and app, and it worked immediately.

When I returned to the affected Project, I removed several older Project Sources that I no longer needed. I then retried saving a response that had previously failed.

It worked!

This makes me wonder whether there’s an undocumented limit on saved-response sources, or perhaps a bug affecting Projects once their source collections become sufficiently large.

I cannot confirm a specific numerical limit, and I’m not claiming that 100 or 101 is definitely the maximum.

Expected behaviour: Eligible responses should save reliably. If a Project has reached a source limit, the app should explain that clearly and ideally display the maximum and remaining capacity.

Actual behaviour: The operation fails with a generic error, without explaining whether this is a capacity restriction, a temporary failure or another problem.

Reproduction

These are the steps I followed:

  1. Open a Project containing approximately 101 individually saved assistant-response sources.
  2. Open a conversation within that Project.
  3. Select an assistant response and choose Add to project sources.
  4. The app displays “Couldn’t update project sources. Please try again.”
  5. Retry with other responses. In my test, three consecutive attempts failed.
  6. Switch to a different Project and try saving a response. This succeeds.
  7. Return to the affected Project and remove several older, unnecessary saved sources.
  8. Retry saving a previously unsuccessful response. The operation now succeeds.

The removal of existing sources appears to have influenced whether another source could be added, although I haven’t established the exact cause.

Diagnostics

Original incident: 27 August 2026 (UK time, BST, UTC+1).

  • 7:23 PM: Project Source save failed.
  • 7:27 PM: Another save failed.
  • 7:32 PM: Third consecutive failure.
  • 7:34 PM: Saving a response in a different Project succeeded.
  • 7:36 PM: Saving in the original Project succeeded after removing several older sources.

Frequency: Three consecutive failures during the documented test. Similar problems have recurred while using large Projects.

Available evidence: I have screenshots showing the error message, a successful save in a different Project, and a successful save in the originally affected Project after removing some older sources.

I would really appreciate clarification on whether saved assistant-response sources have a documented or undocumented numerical limit, and whether this behaviour is expected.

If anyone else has encountered this with large Projects, I’d love to hear about it, because this feature is incredibly useful for keeping track of long-running conversations and established information.

Thanks!