Note: Worth mentioning, I am no technician, so if there is a fix for this that i can apply on my end, if possible, a step by step instruction would be lovely ;)

Hi @Dahnic , can you let me know which trigger you are using and how it is configured?

Thanks for the speedy reply, the Solution consists of 7 different flows, so the triggers they are using are:

1. Recurrence (Scheduled) - Monthly, followed by 'Get items'

2. Recurrence (Scheduled) - Monthly, followed by 'Get items'

3. Recurrence (Scheduled) - Monthly, followed by 'Get items'

4. Recurrence (Scheduled) - Daily at 23:00 followed by Initiate Variable (and then Get Items)

5. Recurrence (Scheduled) - Every 30 mins, followed by Initiate Variable (and then Get Items)

6. 'When a row gets added, modified or deleted' (Dataverse) - ChangeType: Modified, Table: Accounts, Scope: Organization - Followed by a branching into two conditions controls for specific a 'Status' Value

7. 'When a row gets added, modified or deleted' (Dataverse) - ChangeType: Modified, Table: Accounts, Scope: Organization - Followed by a Compose action (and then a Parse Json)

I have a similar problem. However, my solution doesn't exist of any flows. It only consists of one Canvas App and seven Dataverse (for Teams) Tables:

I have a similar problem. However, my solution doesn't exist of any flows. It only consists of one Canvas App and seven Dataverse (for Teams) Tables:

Can you try the latest release (https://github.com/modery/PowerDocu/releases/tag/v-1.2.0) and see if the problem still happens? Made a smaller change, curious if that helps.

Looking at implementing some improved error handling in the future, so that it's easier to figure out why things go wrong

Hi @modery, I just tested it with the new version. Unfortunately, I get the exact same error message.

Update: Though it still throws the same error message, it now also generates the documents using the new version (1.2.0). I just haven't checked earlier, because I didn't expect it to generate anything after receiving the error message.
The documents also have content in them, but I'm not sure if they're complete or not.

The error occurs during the last step of the documentation process, once it tries to document the solution overall. By then all Flows and apps have been fully documented already.

Could you share the solution.xml file located in your .ZIP solution with me? Parsing this file fails as per the screenshot you shared. You can share it either through here or via rene@modery.net

Thanks for sharing the file, @Hannes97 . Managed to fix the issue, will be included in the next release

Latest release is now available: https://github.com/modery/PowerDocu/releases/tag/v-1.2.1
Please let me know if your issue still occurs, @Hannes97

Hi @modery,
I tried your latest release (v-1.2.2) and got the following error message:

However, it again seemed to have generated the documentation just fine. Perhaps a success pop-up would be nice to enhance the UX a bit.