Hey, thanks for the reply. It made me realize the problem wasn’t with nodecanvas itself , but with the way we used our continue button to travel to the next dialogue node. this button never got disabled and thus allowed us to continue to the next node regardless of whether their was an action being executed currently or not. I made a workaround by sending an extra subtitlerequest when a dialoguenode ends , this request doesn’t have a continue actio nattached to it and does makes the continue button call nothing untill the actio nis fixed and we get teh next proper subtitlerequest of a regular dialoguenode.
dyconic
