This should be every builder’s first step when they run into any kind of weird issue related to actions in their GPTs.
Basically, turn it off and on again.
GPTs can exist in some kind of weird limbo state where broken code/instructions are somehow cached. This usually, but not always, happens after a weird, broken call to an API endpoint occurs or the GPT is saved with a malformed schema.[^I haven’t had the time or inclination to dive deeply into trying to find a reproducible way to break a GPT in this manner, anyone has insights here it would be useful to collect them as reproducible examples can be fixed.]
The most reliable ways to remedy this in order of destructiveness,
- Delete the action and recreate it. If the schema is good, it’s as simple as cutting and pasting it.
- Delete the GPT and recreate it. Same as Number 1 with a bit more copying and pasting and possibly some file uploads.
Try Number 1 first a couple of times before resorting to Number 2.
Anecdotally, there are reports that increasing the version number of the OpenAPI schema can help nudge the GPT out of the state it’s stuck in.