Workflow designer hangs in updating activity values while editing
We have some pretty involved workflows and have been having pretty frequent issues with Workflow Designer (on prem) not updating the edited values as they are entered. I have found that if the intellisense is not showing values as you type that it is in this hung state. If I wait it out (can be several minutes) it eventually catches up and will respond again for a while before hanging again. It is rather maddening and slows development down a fair bit waiting for designer to be responsive again.
I have tried restarting the GeocortexWorkflow app pool, restarting the browser, trying a different browser, only having one tab open, and still hit the same issues.
Anyone else having these issues? Is there a way to turn off intellisense if that is the problem of it needing to cycle through the workflow verifying values all the time?
--Marc
-
We are on Workflow Designer 5.23.1.
0 -
I have had small hangups, but at that point I've always been able to split some chunk of workflow logic out into a child workflow. I'm sure you've already considered that, but just in case you haven't I want to be sure to bring it up since it *could* be a quick fix.
0 -
Yeah, we have already split up the workflow into three separate workflows already but still have this issue. It seems to be the worst in what is essentially our "config" workflow that sets specific values to pass into the other workflows, so it is essentially just setting up a big structured json object but using the workflow UI to make it navigable.
--Marc
0 -
Hi @Marc Rempel? can you please email us at support@geocortex.com to get a support case going for this? If you could also provide the workflow you're working on, we'll be able to dig into this and help troubleshoot.
Thanks
Gareth Evans (he/him) | Product Support Analyst
0 -
Hi @Gareth Evans? . I submitted a support case request along with an example workflow. Thanks.
Marc
0 -
Was this issue ever addressed or resolved by VertiGIS? I have the same issue with Workflow 5.35 (on-prem). If it has to do with some limitation on the complexity of any given workflow, what should we be looking to avoid?
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
6 kommentarer