You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When starting the documentation process for a Power Automate solution I get instanly the error 'Object reference not set to an instance of an object'
To Reproduce
Steps to reproduce the behavior:
Go to Select Apps, Flows, ro Solutions... ... etc.
Select my Power Automate solution.zip
Click on start documentation process for selected files
See error
Expected behavior
starting the documentation process.
Screenshots
Flow Used
If possible, please share the Flow that caused the error. This will help with any troubleshooting, debugging, and improving the solution
The text was updated successfully, but these errors were encountered:
The error occurs while trying to parse a Flow. Which trigger are you using? Is it possible for you to share the code for it here so that I can try to replicate the issue?
In the new designer, when you edit the trigger, there is a tab called "Code View", for example:
I'm also facing the same error.
I think problem is with processing the solution files. If I try to generate document for exported flow (zip), it works, but if I do it for exported solution(zip), it throws the same error "Object reference not set to an instance of an object"
I've seen this error when PowerDocu is trying to parse Desktop Flows. This has been handled in the most recent code update, which will be included in the next release. Not out yet, will post here again once it is available
Describe the bug
When starting the documentation process for a Power Automate solution I get instanly the error 'Object reference not set to an instance of an object'
To Reproduce
Steps to reproduce the behavior:
Expected behavior
starting the documentation process.
Screenshots

Flow Used
If possible, please share the Flow that caused the error. This will help with any troubleshooting, debugging, and improving the solution
The text was updated successfully, but these errors were encountered: