I have a sequence which contains only one invoke workflow(GetTimeStampViaAPI).
But strangely, the time taken by the sequence is 3m 2s 34ms and the Invoke Workflow takes only 1m 7s 82ms. Where is the difference of time lost?
If Invoke Workflow takes only 1m 7s 82ms, shouldn’t sequence also take nearly the same?
This might be due to previous session data is also reflecting there. Try deleting old session data from this location C:\Users\username\AppData\Local\UiPath\ProfiledRuns and do one more execution.
This should give you the correct timelines.
Thanks,
Ashok 
@ashokkarale , thanks for your reply.
I have tried by deleting the files also. It is not helping. Still there is a difference of time between the Sequence and Invoke Workflow.
Ohh ok. Tried restarting Studio as well?
Yes. Machine restart as well.
I can confirm that the profiling panel is not showing previous execution times as the output panel run time and profile panel runtimes match exactly. Hence, we can say that the runtimes mentioned belong to current run/ session only.
Can you share whole screenshot from Profiler panel?
All percentages next to each workflow should add up to 100%.
Edit:
Ooops, now I read that again and realized what this question is about. I find it interesting that Comment block alone takes 16s. Do you have maybe a lot of arguments, or they contain a lot of data? What happens if you remove that Comment and just leave single Invoke Workflow activity inside that sequence? Does using Run vs Debug change anything? Please, preferable make several runs.
Comment is not taking 16s, it is merely 16ms. Lot of Arguments is not the case here. I have uploaded the XAML to orchestrator tenent as a package and have replaced the XAML by the activity. This resolved the issue. Strange but thats how it works it seems.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
