Chatbot link is not working suddenly

%3CLINGO-SUB%20id%3D%22lingo-sub-2568707%22%20slang%3D%22en-US%22%3EChatbot%20link%20is%20not%20working%20suddenly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2568707%22%20slang%3D%22en-US%22%3EHello%20Team%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20created%20a%20Chatbot%20and%20shared%20it%20within%20my%20organization%20via%20teams%20and%20it%20was%20working%20fine.%20But%20suddenly%20from%20yesterday%20we%20are%20receiving%20app%20does%20not%20exist%20%2F%20your%20organization%20might%20have%20blocked%20it.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20looks%20like%20a%20global%20issue%20with%20custombots%20an%20API%20is%20throwing%20an%20error.%3CBR%20%2F%3E%3CBR%20%2F%3ECan%20you%20please%20take%20a%20look%20at%20this%20and%20fix%20it%20ASAP%3F%3CBR%20%2F%3EAPI%20throws%20400%20error%2C%20attached.%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2568707%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBots%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2580283%22%20slang%3D%22en-US%22%3ERe%3A%20Chatbot%20link%20is%20not%20working%20suddenly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2580283%22%20slang%3D%22en-US%22%3EHi%2C%20Looks%20like%20you%20are%20using%20beta%20API.%20Could%20you%20please%20try%20using%20the%20production%20version%2C%20if%20it%20is%20available.%3C%2FLINGO-BODY%3E
New Contributor
Hello Team,

I created a Chatbot and shared it within my organization via teams and it was working fine. But suddenly from yesterday we are receiving app does not exist / your organization might have blocked it.

This looks like a global issue with custombots an API is throwing an error.

Can you please take a look at this and fix it ASAP?
API throws 400 error, attached.
4 Replies
Hi, Looks like you are using beta API. Could you please try using the production version, if it is available.
Thanks Prithvi. I have no control over the api. It's coming from Microsoft code.

However I was able to font the issue causing flow also raised a suggestion to MSFT to provide name of the flow in error instead of something Gibberish.

I got the name of the flow causing problem in the result of that failing api in developer tools > network tab
Hi, So were you able to track the issue causing the problem ?
Yes. I was able to resolve the issue.

It's not the new flow I added causing but an existing flow whose parameters for changed.