Open Icidis opened 11 months ago
Hi, i see the same error on my side. Any news on that issue?
Thanks for providing the workflow definition and instance JSON exports.
I am not able to reproduce this issue with the latest version and will close the issue as such. However, please feel free to reopen if you can still reproduce this issue with the latest version. Thank you.
Hi @sfmskywalker, Sometimes, I encounter the same error with Elsa 3.2.0-rc3 on my end (around three times), but I haven't been able to reliably reproduce it. It usually happens when navigating between screens. cc @Icidis
hello @sfmskywalker, i have same problem in elsa 3 !!!!
Reopened for another round of triage.
Hi @sfmskywalker, I was able to reproduce the issue with the following steps: Note this is not the only way the error occurs, it's just one case.
This issue doesn't always occur on the first attempt, so if you're unable to reproduce it initially, please try it again. This is the video when I try to reproduce it.
https://github.com/user-attachments/assets/7aaac79c-8fab-4eef-8ef4-05d04c972f4f
Let me know if you need further details or clarification!
@TimNguyenVN Thank you for the additional details and video. I have tried to reproduce the issue accordingly with the current version of the main branch, with no avail. However, when switching between two tabs (1 tab for the sub workflow and another tab for the consuming workflow), I do notice that, without refreshing the consuming workflow tab before executing the activity, the activity dissapears. I suspect that this has something to do with the activity registry getting out of sync, which would be a separate issue.
When you get a chance, it would be interesting to see if you can still reproduce the issue with the 3.3 release happening later this year.
Hi,
When trying to view the workflow definition instance I'm getting the following error and the designer disappears:
Definition: example_-user-task-workflow-definition.json
Workflow Instance: d02621bfc80f4ff3.json
Also note: When doing this for a different workflow definition that only does write-lines and no suspending state it works perfectly.
If anyone has an idea why the cause could be it would be helpful.