Ending Job Execution After Last Activity Takes Around 40 secs

Feedback Studio
,
1

Hello There,

I am currently working on creating a library of reusable workflows. I’ve started with a component for login. After executing all activities it takes around 40secs to end the execution on Studio.

I am using the following versions of packages and Studio 22.10.4 .
image

image
image1802×906 74.4 KB

image
image1768×828 85.9 KB

3

You screenshots show it takes less than a second between the log message that the workflow is completed and the log message from studio saying Execution ended. It does not support your report that it takes 40 seconds.

4

Hello Jon,

Please take a look again, timeStamp is showing as hh:mm:ss and there are exactly 38 secs in between two screenshots.

Thanks

5

Ah ok, I was reading the timestamp as mm:ss:ff, apologies.

Does it still take 40 seconds if you run the workflow instead of debug it?

6

No problem.
Yes, it does. I haven’t debugged it actually.

7

Strange behaviour indeed. I would suggest seeing if this is related to this workflow alone or if others do it. Perhaps test with a workflow just containing a few log messages. By process of elimination we can try to determine if its related to the Library as a whole (libraries as a whole) or just the workflow.

I use libraries extensively and never encountered this issue. My gut says some weird logging is happened behind the scenes here at the end of the running.

8

So basically the workflow includes Get Credential activity - logs - Use Browser (including 3 Ui Activities). When I deactivate Use Browser scope, execution finishes in a second

10

Most likely you have the Use Browser activity looking for a selector. The automation execution can be delayed if the target page is not available or it takes a while to appear on the screen.

11

Hello Alexandru,

Actually, after running all activities in the flow, it takes 40 secs to finish the execution. I even added write line activity at the bottom to be sure about it.

Thank you

12

Does the same happen on a blank new project, or only on this particular one?

It would help if you could share a dummy, sample project that reproduces the issue. It sounds really strange.

13

Hello,

I happens only on this one. I don’t think it is possible to reproduce the issue with a dummy project since it happens after logging into a private salesforce endpoint.

Thanks,