You’re offline. This is a read only version of the page.
13
Hi
I'm currently facing the issue that when I add a specific 'Go to Topic' node it gives me 2 random output variables and an error.
My PVA is in dutch, but the translation should be like: "Outputvariable for this topic has been changed. Save current topic".
Has anyone seen this error before?
What to do about it?
Kind regards
Hi @JBeutels,
Great you found a solution and thanks sharing it.
Geen probleem. Always happy to help out 🙂
I've copied the FOSS flow, redid the 'Go to Topic'-node and there were no more errors so it seems to be a bug in the system.
If I find a way to report it I will 🙂
Thanks again!
Thanks for the reply.
The setup is 'simple', just a couple of flows with Say, Full Response capture, Boolean & Multiple Choice question nodes.
The FOSS Flow is quite long & extensive and has 29 topic-variables that ware used within the FOSS Topic. There are also 5 bot-variables but those are just the default ones.
Those topic-variables are captured and inputted in one of 24 Power Automate Flows that send an e-mail with the necessary information depending on the choices made in the FOSS Flow.
Hereby the settings of the automatically created Variables in the Go To Topic-node.
The settings of the Topic Variables in FOSS are as follows. None of them either receive or return Values and are all on Topic-level.
I have done some testing so there are some variables that have recently changed, but only after the issue came up.
If the integrity of FOSS NL has been compromised, maybe it's advised to export the topic and import it again?
Kind regards
Hi @JBeutels,
No, I have not seen that one before. Can you share the setup of your FOSS NL topic?
What are the usage settings of the variables used in their? And have they been changed recently?
I would first double check if the FOSS NL topic is still in a good state.
#1
Romain The Low-Code...
76
#2
Pablo Roldan
61
#3
stampcoin
10
Share
Report
All responses (
Answers (
