Answered

0 System Topics: corrupted bot file or copilot studio upgrade bug?

Like (0) Share

Report

Posted on 21 Mar 2024 14:35:38 by OOO1337777

The latest bot stop working overnight.. it now says "0 Topics"and"0 System" topics. Yesterday it was testing OK.... corrupted bot file or copilot studio upgrade bug?

Some other different bots are still working ok.

This is getting silly, I expect a reverse payment or refund for my time wasted on buggy software.

copilot studio down Capture.PNG

Categories:

General

All responses (3)

Answers (1)

remidyon on 21 Mar 2024 at 18:09:55

Like (0)

Report

Re: 0 System Topics: corrupted bot file or copilot studio upgrade bug?

Hey @OOO1337777

I'm glad everything is back in order, thanks for reaching out!
OOO1337777 37 on 21 Mar 2024 at 17:59:48

Like (1)

Report

Re: 0 System Topics: corrupted bot file or copilot studio upgrade bug?

anyway I just recreated a second bot with all the new topics and copied-pasted over the YAML source file from a backup copy I had using copilot studio source code editor view, verbatim copy-paste and now the second bot works magically...

but then in the meantime I went ahead dug into the dataverse environment url and clicked a bunch of stuff without really modifying anything (I loaded the Obi Data column view but did not touch its content)... now magically the first older problematic bot has restarted working again... I dont know the reason, maybe a maintenance task on the microsoft side has just finished or maybe simply loading the dataverse content has auto-corrected itself from any corrupt string?

whatever
Verified answer

remidyon on 21 Mar 2024 at 17:02:17

Like (0)

Report
Re: 0 System Topics: corrupted bot file or copilot studio upgrade bug?

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