Same issue here — really relieved to find this thread.
I’ve been debugging since this morning. Checked my domain, DNS, and all my endpoints. On the server side, everything works as expected.
I tested a few features and here’s what I found (hopefully this helps the team investigating this issue):
The key problem seems also be a UI issue. Previously, whenever a request involved login or modifying/deleting data, a “Login to your website” or “Confirm” button would appear. That button is now gone, which means users can no longer authorize these requests. As a result, every request that requires modification or deletion now returns something like this:
{
"function_name": "delete_project_api_projects__project_id__delete",
"domain": "my-domain-name",
"message": "The requested action requires approval",
"action_id": "g-26a1aa9cd5f6d11cfabdaa173e5abf572cd4ef21"
}
Since the button has disappeared, users cannot log in or grant the necessary permissions to proceed with the Action.
As a workaround, I found that going through GPT → See Details → Privacy & Safety → Connected Accounts → Login allows login to succeed.
Up until about an hour ago, I was still able to run GET requests. But after re-logging in, even GET requests no longer work.
Update:
Now even GET requests are returning the same approval message, despite being marked as non-consequential:
// [debug] Calling HTTP endpoint
{
"domain": "matt.youseminar.cn",
"method": "get",
"path": "/api/projects/",
"operation": "get_my_projects_api_projects__get",
"operation_hash": "d4e6bf0979b7677c3f8618f4dd162ad539494f54",
"is_consequential": false,
"params": {}
}
// [debug] Response received
{
"function_name": "get_my_projects_api_projects__get",
"domain": "matt.youseminar.cn",
"message": "The requested action requires approval",
"action_id": "g-26a1aa9cd5f6d11cfabdaa173e5abf572cd4ef21"
}
This makes it impossible to perform even basic read operations. It seems like the approval flow is being incorrectly applied globally, not just to destructive actions.
Update Again
Thanks to @dkakeith for pointing out @iyvljtjqleyj’s post. I clearly remember setting the Privacy Settings to always allow when I first started using this GPT. But after double-checking just now, I noticed that on the web version it had somehow reverted back to ask. I switched it back to always allow again.
Now the GET requests are working for me — but PUT, DELETE, and POST are still not functioning.
This custom GPT is something my friends and I use every day, so it’s quite concerning. Right now I don’t even know where the issue lies or when it might be fixed.