Unable to Publish bot. No Errors?

(4) Share

Report

Posted on by Bdstm

Hi,

I'm trying to Publish my bot in order to reflect a number of changes made over the last 2 weeks.

The wizard starts, indicating that it's publishing latest content, and after about 5-10 or so minutes (much longer than normal), just goes away with no errors, or any indication of incomplete operation.

Bot has been published in the past, the most recent instance is of 19 days ago.

Another bot under the same ownership publishes with no issues.

Currently running in trial mode with a license purchased last week and awaiting provisioning.

After the message goes away, refreshing the page does not indicate the most recent update.

Any ideas?
Thanks!

Categories:

Publish & channel management

I have the same question (0)

All responses (19)

Answers (0)

Sort by

DebacManikandan 5 on at

Like (0)

Report
Copy link

Link copied!

Hi, I am facing the exact same issue. I have another bot for which the publishing works normal as well. The only difference between those two bots are that - the first bot that works normally uses "Production" Bot Type, and the second bot that fails to publish uses the "Preview" Bot Type.

Are you having the above issue with "Preview" Bot Type or is it "Production"?
Any help around the above from anyone would be much appreciated 🙂

Was this reply helpful? Yes No
CU22081450-0 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @Bdstm @DebacManikandan ,

Did you try to send 'start over' to the bot?

This phrase is resetting the bot's conversation.

Was this reply helpful? Yes No
Bdstm 16 on at

Like (0)

Report
Copy link

Link copied!

Yes, same experience, the preview bot is failing to publish, while production bot published fine.
However, I did create a new bot to test the behavior, pushed it to Preview but did not create any topics or modify the existing ones - that one published fine. I do however suspect that this is "preview" related.

Was this reply helpful? Yes No
Bdstm 16 on at

Like (0)

Report
Copy link

Link copied!

Renato, I sent the command but it didn't help.
I discovered a new issue today, I had turned off some topics during testing to see if they cause the issue. My primary topic is now unable to turn back on and when I try to edit, the entire page is empty. This appears to be a bug and it has cleared a lot of content that we spent 3-4 weeks building. The error message is: Diagnostic Trace Id: Unexpected error: {}.

I don't have a way to recover the topic. I`ll attempt to rebuild it now to see if it fixes the issues.

Was this reply helpful? Yes No
DebacManikandan 5 on at

Like (0)

Report
Copy link

Link copied!

@renatoromao- yep, did try using "start over" several times, although I don't understand how that will have an impact with the publishing of the bot by itself.

As @Bdstm mentioned I received the same "Diagnostic Trace Id" error message and have lost all the components built inside the topics.

Am leaning more towards it being a "Preview" feature issue. The "Production" type bot isn't good enough yet - that it doesn't even have the "clear variables" to do a clean start over. This forces us to use the "Preview" type bot. Any help around this from the Microsoft team would be much appreciated.

Was this reply helpful? Yes No
inzil2k 192 on at

Like (0)

Report
Copy link

Link copied!

I had a similar issue with the preview bot. Publishing did not work due to an error in some topic but no topics were displaying any errors. I tried turning topics off one by one but could not find a topic that had an issue. In the end, I had to create a new bot. Hopefully this wont be a problem once the preview version goes GA this month...

Was this reply helpful? Yes No
Bdstm 16 on at

Like (0)

Report
Copy link

Link copied!

That's my hope as well. Thanks to your update I checked and it does look like all planned updates are due June 2023 (except multilingual). Hopefully that will add some stability, though it is a bit concerning that this major issue is present so close to public release. Hope to hear from Microsoft on this topic.

This is the 2nd major issue we experienced, having lost a "topic" a few weeks ago and having to rebuild it from scratch.

Was this reply helpful? Yes No
Jameslew_MSFT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi all, sorry you're encountering this issue. I'm hearing this has been since Monday. Have any of you filed support tickets such that the engineering team can investigate your specific environments?

Was this reply helpful? Yes No
Bdstm 16 on at

Like (0)

Report
Copy link

Link copied!

Hi, thanks for your reply and glad to have the Microsoft team engaged with us. I have not submitted a ticket, would you be able to provide a link to the correct site where I can do so? I would love to bring it up to the engineering team's attention.

Thanks

Was this reply helpful? Yes No
Jameslew_MSFT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

We identified an issue and are working with the team that owns it to see if they can provide us an ETA for a hot fix. If necessary, there is a workaround that PVA product support could help you apply to your environment.

Again, sorry for the disruption and thank you for reporting.

Was this reply helpful? Yes No