REGRESSION: Free ChatGPT accounts unable to invoke apps!

Thanks for the share, could you both please send me conversation IDs?

We have tried this with multiple approved Chatgpt MCP Apps. It triggers internet search despite the MCP Apps being connected and tagged except under 2 scenarios:

  1. If the ‘Web Search’ Setting is disabled under Personalisation Settings

  2. If the account is either Pro

    Attaching a few example conversations for your reference:

    1. 6a1d2880-01ac-8321-8dea-5659200f118c

    2. 6a1d29af-e4b4-8323-8d7e-8848c4d4e986

here are some examples :
6a1c9252-ca0c-83eb-9bd0-694642e88ca0
6a1d32f4-f6cc-83eb-a108-95485922c0f2
6a1d3367-b824-83eb-a9b6-b2c40c7db70b
6a1d3342-c3cc-83eb-a24e-8f221492ca91

and this one with tripadvisor : 6a1d34d4-24b4-83eb-b466-39aaebbb5e59

6a1d3be2-8ce8-83eb-bb8c-6acbbdec2643

I am also seeing this behaviour across the past few days.

Another possible piece of the puzzle - if I enable “Connector Search” in Settings > Personalization > Advanced, our app appears to work. This is true with “Web Search” still enabled.

Note that conversations still invoke the web_search api tool initially but then immediately pivot to invoking our tool (and never display results from the web_search).

Example: 6a1d68ed-ade8-83eb-9e5a-3b08070e7f90 / 6a1d6adb-6e0c-83eb-8c67-09cdc6e2078a

Thanks for the tip! just tested with “Connector Search” enabled (while keeping Web Search on) but unfortunately it doesn’t change anything on my end — the web_search tool is still called and its results are actually used in the final response, with no pivot to our connector.

I tested further and discovered that this change has helped, but has NOT eliminated the problem. The Web Search tool is still being called in place of our app for some query formats.

As others have concluded, from my perspective this is almost certainly a prioritization conflict between the web_search tool and others exposed in the chat - with the former being given much higher preference than it should be when explicit tools/apps are also present.

Hey everyone, Wanted to share an update that we are still working on fixing this issue actively. I will inform everyone here once we have a fix in place. Thank you for raising this in community!

Hey all, we rolled out another potential fix late yesterday. I’ve already heard some good feedback on it, but please do surface if you’re still running into this!

Thanks for the update! Based on our initial testing, things look much better. The broken behavior still seems to occur occasionally, but very rarely and we haven’t been able to identify a reproduction pattern yet.

Thanks for the fix — if we manage to spot anything that could explain why it still happens from time to time, we’ll report back here. Encouraging progress nonetheless!

Glad the issue is now resolved. We are aware that you might face it time and again so if that happens please feel free to start a new thread and link this one. For the purpose of tracking. We will close this thread for now.

Thanks a million for flagging this issue and assisting us with the details. We really appreciate all the help.