Unable to find logs in PowerAutomate Desktop after/during the process execution.

(0) Share

Report

Posted on by Santosh7

Hey Team,

We are unable to find/locate the logs in PA Desktop after/during the process execution. Can you please help on this ?

Categories:

Power Automate Desktop

I have the same question (0)

All responses (7)

Answers (0)

Sort by

VishnuReddy1997 2,666 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Santosh7 ,

You can view or find the logs of Desktop flow in cloud that is make.powerautomate.com
When you open the above website you can see an option called Desktop flows activity as shown in below image.

After that if you select your particular desktop flow and if you view details as shown in below image you can see all the logs action wise.

Note: If u have solved your issue Please mark it as solution.

Regards,
Vishnu Reddy

Was this reply helpful? Yes No
Agnius Bartninkas Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Please note that what @VishnuReddy1997 suggests only works if you have a paid license of Power Automate. If you do not, there are no logs you can view.

To have proper logs, you need to implement your own custom logging functionality by adding actions to write logs to some kind of a file, or a database or whatever you want.

Was this reply helpful? Yes No
Santosh7 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Hey, Thanks for sharing your response. We are aware that we can find the logs in cloud and dataverse table as well. Trying to find a way if we can extract/dump logs to a local file in real time. Thank you!

Was this reply helpful? Yes No
Santosh7 4 on at

Like
a
(0)

Report
Copy link

Link copied!

Hey, Thanks for sharing. Did you ever come across a similar use-case or is there a library/marketplace so that we can pick it up and make changes to it?

Was this reply helpful? Yes No
Deenuji_Loganathan_ 6,255 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

@Santosh7

you can build your own mechanism using custom actions. if you feel its more complex then i would recommend you to use "Write text to file" something like below.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀. If you'd like to appreciate me, please write a LinkedIn recommendation 🙏

Was this reply helpful? Yes No
VishnuReddy1997 2,666 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Santosh7 ,

Please find some samples of Use case how to write logs to text file.

Case1: First you need to setup the variables as shown in the below image and need to call or run that subflow to write the log to the text file as shown in image 1.

Image 1:

Case 2: You need to setup in on error to write the error message logs to text file as shown in below image 2.

Image 2:

Case 3: Create a sub flow as shown image 3 and call it wherever it is required.

image 3:

Case 4: It will write to the text file as shown in image 4:

(Note:- if you got your solution you can mark as solution and gives kudos)

Thanks & Regards
Vishnu Reddy

Was this reply helpful? Yes No
Agnius Bartninkas Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!
The way I would recommend creating logs is as follows:

Encapsulate entire sub-flows with an On block error action. Make sure to enable the "Capture unexpected logic errors" toggle on the block - this is really the only way to capture ALL errors in PAD properly.

Add a sub-flow for logging. Call it whatever you want.

Add the Get last error action to the logging sub-flow. This will retrieve the error details (the action that failed, the sub-flow where that action resides, the error message, etc.).

Add a Write text to file action to log the message to a text file.

Make the On block error created in step 1 call the logging sub-flow on error.

If you also want to do some non-error logging, too, you can also modify the logging sub-flow a bit, to have a condition that checks whether or not you actually called the sub-flow from On block error. You would then need to set some kind of a variable in the block, too, so you can check it in the condition. And then you would only use the Get last error action if there is an error to capture. Otherwise, log whatever message was provided as inputs to the sub-flow (via a Set variable action in the parent). This can then be used for business exceptions, info logs, etc.

Was this reply helpful? Yes No