I am experiencing extreme long loading times when navigating to another page if I activated a workflow. Is this a temporary issue or do I misunderstand the concept of server API’s? The reason why I use API workflows is that many of my workflows involves updating lists with a deep search queries.
So what I am experiencing know is (I have 2 pages in the app) if I open page 1 it loads fast. If I navigate to the second page it lost real fast. Now I do something on one of the pages and try to navigate to the other page then the page hangs for one minute before it navigates to the other page.
I figured out if I do a simple autobinding workflow it does not slowdown. Otreally are the API server workflow. I also played with the parameter keys. I reduced one API workflow to only the “parent group user” and do all searches on the API endpoint. Still this API workflow resulted in a one minute delay of navigating to the next page.
Is this a temoporary issue or do server API’s need to have the page opened when for example the key is “parent groups user”?
Verify your logs with cpu usage, and the plan you are on. API and workflows has been separated on sharing resources. One or the other isn’t supposed to affect performance.
It is waiting for the whole list to have their API workflows scheduled (but not run) before doing the page nav. That is why it is slow, rather than CPU.