A bit like 1-2 months ago when 5.2 or 5.1 was first released, all of my custom GPT using Actions that call a webhook towards Make Integomat stopped working.
1-2 months ago, the call to the connector would appear but no “Confirm” or “Deny” button would appear.
Today, all my Custom GPT started saying that they used the action, but no call to the connector are made. When I switch to Legacy Model 4o, than the call is indeed made to the connector.
I actually had a similar problem, custom action that had been working for weeks suddenly stopped working today. I dont know why but switching to 5.2 auto fixed it.
When using 5.2 thinking, even if I gave it the full tool name e.g. ‘…jit_plugin.get_folder_directory’ it would get confused and start invoking its code interpreter or web search every single time.
Hey @Philippe_Plourde, yeah, that’s definitely frustrating, especially if it was working before. If 4o is triggering the action but 5.x says it used it without actually calling it, this could be something like a cached session or how that variant is handling external actions.
A few quick things I’d try:
If you can share a bit more detail around when this started and whether it’s consistent across runs, we can dig into it further. You may also want to compare your setup against the GPT Actions getting started guide to make sure everything aligns with the current implementation.
I also am having this issue of Actions not being called but working sometime but with a complete loss of consistency. Several weeks ago it work like clockwork now it can fail for seemingly no reason but when I go to the TEST action environment it works nearly always no matter what model.
Any news on why this is happening?
I am also having a same issue with GPT 5.4 in thinking mode. If I change the mode to Auto or 5.3 Instant, it calls the API tools consistently.
Note: I have created new GPT from scratch.