It looks like this is the action "Office 365 Create List Item Or Document Set" that is the cause of the problem.

Soooooo, I changed the action to the other one "Create List Item".

It works great BUT I can't create an item in a folder with this one.

When i Add a field to the action, there is a field "Folder" but I don't really know what this field does. When i select the name of an existing folder or its ID, it just creates the item but not in the folder. 

I tried with the folder's path and with the name AND the Content type ID, but still nothing.

So I used the action "Office 365 Create List Item Or Document Set" just to create the item in the folder and after, I use the action "Update List Item" but I have the same problem than before : Sometimes, the "Office 365 Create List Item Or Document Set" does nothing. The workflow status is still "Started" without any errors.

Is there a way to create an item in a specific folder without using this bugging action ?

Thank you.

Regards,

Pierre Nouet

Hi ‌

Did you find a resolution for this?

I have an O365 workflow, it's looping through a bunch of attachment controls and pulling the attachments out and putting them into a library using the Upload to O365 action. It seems to get to around 13 or 14 items and then just stops. The workflow status is still on "Started", but the workflow is no longer continuing.

Hi Ryan Greenaway, 

I didn't find a resolution for this.

But I used the action "Create List Item" instead of the O365 action. And it works, but not with the folders.

I used the folder to manage the permissions foreach item. 
Now, I make unique permissions foreach item, this is really bad i know but I can't do anything else.

I also use the "Upload to O365 action" for some attachments but i didn't test with that much attachments.

I'll test with 15 attachments next week to see if I have the same issue and I'll come back to you.

Regards.

I believe I found the issue here to be O365 resources.

I had an item with some 50+ attachments and the workflow was looping through copying the attachments into a library using the O365 Upload to SharePoint action. It would generally copy around 14 items and then fall over. I found this article on safe looping and removed the "Log to History List" actions and inserted a "Pause for Duration" at the end of each loop, pausing the workflow for 1 minute. It now means means my workflow is slow, but at least it's completing. It's all part of the measures MS have in place to stop a workflow hogging resources on a tenant. I would suggest that the "Create List Item" action is less resource hungry than the O365 action (for whatever reason) and therefore you don't encounter any safe looping safe guards. 

Oh yes, that's what i thought too. And I tested it, but my workflow would last for more than one hour so i could't take it.

But yes, that's a solution.