'Please call loadWorkflow before using the designer' error when editing the automation/flow

[rhiheu]

Hi,

My automation/flow just stopped firing on the 21/4/20. It is due to trigger and send an email when a new item is created on a SharePoint list. I'm seeing an error when trying to edit it - 'Please call loadWorkflow before using the designer'.

• It's not showing a failed run in the Runs history
• It's not showing any errors in the 'Flow checker'
• Both it's connections (SharePoint and Office 365 Outlook) have green ticks next to them
• I've tried exporting the app, and re-importing it, this error is showing on the new import but the old Flow won't fire either
• The Flow is turned on
• It's on a per user plan, but only runs max 10 times a day so no limit issues I believe
• I've looked in the O365 Admin Center and Microsoft Power Automate's status is listed as 'Healthy' in the Service health section.

I'm not what else to try. Thanks in advance for your help.

[v-litu-msft]

Hi @rhiheu,

Ok, so the issue happened when you try to edit the Flow "When an item is created in SharePoint list".

I tried to reproduce your Flow but not find the same issue, so it is not a service issue.

If you recreate another Flow with the same trigger and monitor the same SharePoint list, will it happen the same issue?

In other words, could you access the SharePoint list normally?

And another way you could have a try is to recreate a new connection of SharePoint, one possibility is that it is caused by connection expired.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[rhiheu]

Hi @v-litu-msft, thanks for your reply. I've been able to get around it by re-importing an old version of the flow and re-building it up to the same point slowly, testing at each step. I haven't hit the same error. I might keep this thread open for a few more days though to see if anyone has any other suggestions as to why it broke though, as it could be a useful reference - the re-building took ages so I would like to avoid having to do that again.

[v-litu-msft]

Hi @rhiheu,

Actually, I met the same error report when I using Flow, but it's not the same trigger, and it just appears once, after I close it and reopen it, it disappears.

Keep this thread open for a few days is a wise decision. If someone could reproduce it and I met it again, I will report it to Power Automate Development Team.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[rhiheu]

Hi @v-litu-msft, thanks for your reply. Since no one seems to have come across the issue, what should I do with this post? It's not exactly 'solved' but I don't know how else to mark it as inactive or something?

Thanks.

[v-litu-msft]

Hi @rhiheu,

There is no other way could do but mark as a solution, It's not exactly 'solved' but you could mark your answer to help other users search the post easier to help you what could try.

Best Regards,
Community Support Team _ Lin Tu

[rhiheu · Accepted solution]

Thanks @v-litu-msft, I've not had this happen again so I'm going to write it off as a random, rare occurrence for now.

[mjeason]

For what it's worth, I had the same problem with a form submission trigger. I simply clicked a different form in the options and then clicked back to what it's supposed to be.  Seems to be a common enough solution in Power Automate.

[MRautenbach]

Hi there,

I have the same problem. I'm doing the lesson (https://learn.microsoft.com/en-us/training/modules/get-started-flows/flow-monitor-incoming-emails) on the Microsoft Learn platform, but when I send an email, the flow doesn't trigger and times out. Has anyone else done this lesson? I thought that it might be because I didn't have a licence for Power Automate, but I got one and it still doesn't work. 

[jaina]

Hi @v-litu-msft ,

I encountered the same error  'Please call loadWorkflow before using the designer'.

I have existing workflows that have been working well for a year already. Earlier, at 7:15 a.m. PH time (GMT+8), I found out that it was not triggering, so I tried to open the workflow, click the test run button, and choose "Manually," and then all the items started triggering. But whenever there are newly created items, it will not trigger. I need to click again on the test manually inside workflow in order to trigger the items.

Can you help me? 

https://powerusers.microsoft.com/t5/Using-Flows/When-an-item-is-created-with-trigger-condition-not-t...

[Anonymous]

Happens to me as well, randomly.  .....EDIT: I just realized that it happened on a flow that got overlapping executions running in parallel and bogging it all down.   For me, I will try setting concurrent maximums to avoid, that may fix it