Hi @OOO1337777
Sorry to hear your copilot broke over night. I am not aware of any problems on bigger scale with our other customers. Seems like it is an isolated incident for now?
It could be that you have a corrupted topic that is blocking your copilot to load.
There is a way to troubleshoot it: you can actually go to the topic record in Dataverse and fix the record by editing the YAML.
First, get your Dataverse environment URL ([DATAVERSE_URL])
It should look like https://org1234.crm.dynamics.com
To get the [DATAVERSE_URL]
- Go to the Overview page of your chatbot
- Click on the solution name - this will open Power Apps
- From Power Apps, click the Settings icon and select Advanced settings.
Then, navigate to this URL:
[DATAVERSE_URL]/main.aspx?pagetype=entitylist&etn=botcomponent
Then use the search to find the corrupted topic.
Look for Multiple Topics Matched
Note: there you could multiple results if you have multiple bots in your environment.
You can use 'Edit columns' and add the parentbotid one to identify the right one.
Enter the record, and copy the content of the Obi Data (data) field:
To self-troubleshoot, you copy the content of the Obi Data field in a text editor or better, VS Code.
The issue is likely that the YAML has empty expressions. So, you must find those and remove them.
It's important you leave the indentation intact in YAML
