I have a bot in which one topic is showing an error in the topic list. As shown below:
However, when I am inside that topic, no error is visible anywhere.
This invisible error is preventing me from publishing the bot
Does anyone have any idea what can cause this and how I could find out what the error in question would be?
I have a rather strict deadline on publishing this and this one has got me completely stumped. I already had to rebuild three topics earlier due to different bugs related to removing a "topic variable (returns values to original topic)" from a linked topic, so kind of behind schedule due to thing outside of my control.
The screen shot suggests that the topic in question has no trigger phrases. That would be an issue and wouldn't show up as an error when editing the topic, because its normal not to have a trigger phrase until after you edit the topic. Add a trigger phrase to that topic and see if that doesn't fix the issue.
There are several topics without trigger phrases without this error. I added one just to test, but that's not the issue. Seems like a bug to me to be honest.
These topics are only meant to be called from other topics, or not called at all and just serve to create bot variables in flows (for images etc)
The next troubleshooting step would be to try deleting and recreating the topic.
Just worked 2 hours doing just that ... same problem appeared.
I guess I need to find a different way of doing things.
Edit : 3 hours later I found the issue. Apparently you can't use brackets in conditions if it's spelled out as a string. The field's value "Other (Related)" came from a different topic, so I couldn't select it as a option value, but had to write it out and PVA did not like that.
I had to use this method of successive due to excessive branching and duplication required when questions branch out and need remerging due to the inability to re-use variables. Successive topics using "receive values from topics" were the workaround to allow remerging, but then caused this issue instead.
yes, special characters can often cause issues. Glad you found the problem and sorry I couldn't have been more help.
No worries, I appreciate the effort.
Looking forward to new version of PVA in any case. Would solve a lot of these workaround pains 🙂
So many events happening this month - don't miss out!
Explore the latest innovations, learn from product experts and partners, level up your skillset, and create connections from around the world.
Learn how to respond rapidly to your customers and employees at scale, using intelligent conversational chatbots.