Describe the bug
My workflow is pretty straightforward and has no loops. At the beginning it makes a request to the server via automaFetch to get some JSON that is used later to control the workflow. The problem is that sometimes (not clear when/how exactly) even though it looks like the workflow worked fine from start to end - it continues making HTTP requests to the server with automaFetch and even ended up dDOSing our own server with billions of save requests sent to the same API endpoint used by Automa :-)
To Reproduce
Steps to reproduce the behavior:
Nothing special, just start the workflow, let it run. The problem will only disappear when I close and start the browser again forcing Automa extension to quit.
Expected behavior
Automa is expected to stop sending requests to the server as soon as workflow is done.
Desktop (please complete the following information):
Describe the bug My workflow is pretty straightforward and has no loops. At the beginning it makes a request to the server via
automaFetchto get some JSON that is used later to control the workflow. The problem is that sometimes (not clear when/how exactly) even though it looks like the workflow worked fine from start to end - it continues making HTTP requests to the server withautomaFetchand even ended up dDOSing our own server with billions of save requests sent to the same API endpoint used by Automa :-)To Reproduce Steps to reproduce the behavior: Nothing special, just start the workflow, let it run. The problem will only disappear when I close and start the browser again forcing Automa extension to quit.
Expected behavior Automa is expected to stop sending requests to the server as soon as workflow is done.
Desktop (please complete the following information):