[Bot Portal] I can't see my bots #6639
Labels
bug
Indicates an unexpected problem or an unintended behavior.
needs-triage
The issue has just been created and it has not been reviewed by the team.
https://dev.botframework.com/
Describe the bug
All my bots have disappeared from the Bot Framework Portal. Despite having previously created and tested bots successfully, as of yesterday, the portal indicates that I have no bots, and attempting to access any bot by its ID returns an error stating that no bot with such an ID exists. Furthermore, creating new bots does not resolve the issue; they fail to appear in the portal post-creation. However, when attempting to use app registration, I'm informed that a bot is already registered with the specified ID, indicating their existence. This issue persists across different accounts, clearing cache, and using different browsers, suggesting a problem with the portal's ability to display or modify bots. This issue severely impacts my workflow as I frequently need to change the bots' endpoint URLs. My Microsoft account associated with these bots is [email protected], and I do not have Azure.
To Reproduce
Steps to reproduce the behavior:
Log in to the Bot Framework Portal.
Notice the absence of any listed bots that were previously created.
Attempt to access a known bot directly via its ID, observe error stating no such bot exists.
Create a new bot, note its failure to appear in the portal.
Attempt app registration for a bot, receive error indicating a bot with that ID is already registered.
Expected behavior
I expected to see all my previously created bots listed within the Bot Framework Portal, be able to access them via their IDs, create new bots that would appear in the portal, and modify my bots as necessary without encountering any errors or discrepancies indicating their non-existence.
Screenshots
Additional context
This issue has been verified across multiple accounts, clearing browser cache, and using different web browsers, all without any change in outcome. Critical to note is that this problem prevents any form of modification to bots, particularly in changing endpoint URLs, which is essential for my use case.
The text was updated successfully, but these errors were encountered: