Logs table is quite slow

[MarkosK]

I am trying to debug a flow that creates a few errors. Every time I navigate to the logs it takes ages to load the list and a few more minutes to filter them and find what I am missing. Is there any alternative that will assist me with the debugging? This is not efficient!

Thnks in advance

[iekosmadakis · Accepted solution]

Hello @MarkosK !
The most straightforward way to debug your flow is by navigating to the upper right corner inside the Flow Designer and selecting the 'Executions' option. From there, you will be able to see all errors associated with your flow and it will definitely assist you with debugging if you combine it with the 'Test' functionality (again within the Flow Designer):

Please consider marking my answer as helpful and accepting it as the solution if it assisted you in any way.

[iekosmadakis · Accepted solution]

Hello @MarkosK !
The most straightforward way to debug your flow is by navigating to the upper right corner inside the Flow Designer and selecting the 'Executions' option. From there, you will be able to see all errors associated with your flow and it will definitely assist you with debugging if you combine it with the 'Test' functionality (again within the Flow Designer):

Please consider marking my answer as helpful and accepting it as the solution if it assisted you in any way.

[MarkosK]

Didn't know the existence of this. Thanks it works for me. Any other useful tip for my debugging?

[iekosmadakis · Accepted solution]

Yep, one more thing that comes from my experience: Open the flow properties > 'Advanced Options' and make sure that the 'Run as' field is configured correctly with the appropriate user. Some users forget to set the option 'Run as' = System User and later when they commit the update set with the flow to upper environments they get errors during the flow’s execution because it contains steps that require admin rights.

Please consider marking my answer as helpful if it assisted you in any way.