Workflow failing since June 29th

%3CLINGO-SUB%20id%3D%22lingo-sub-745783%22%20slang%3D%22en-US%22%3EWorkflow%20failing%20since%20June%2029th%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-745783%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20use%20Office%20365.%20We%20have%20a%20workflow%20(SharePoint%202010)%20that%20sets%20permission%20for%20a%20list%20item.%20It%20fails%20since%20June%2029th.%20Anyone%20else%20has%20issue%20with%20workflows%20recently%3F%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20have%20much%20details%20about%20the%20error.%20Only%20a%20correlation%20ID%20and%20still%20waiting%20for%20Microsoft%20to%20give%20me%20the%20detail%20of%20the%20error%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-750603%22%20slang%3D%22en-US%22%3ERe%3A%20Workflow%20failing%20since%20June%2029th%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-750603%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wasn't%20able%20to%20get%20the%20error%20associated%20with%20this%20correllation%20ID%20from%20the%20Microsoft.com%20support.%20Apparently%20some%20people%20here%20can%20provide%20this%20information%20to%20me%20on%20a%20PM.%20That's%20what%20they%20said...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20fixed%20my%20issue%20by%20modifying%20my%20workflow...%20I%20redone%20an%20IF%20statement%20that%20was%20broken%20for%20unknown%20reason%20and%20now%20it%20work.%20I%20didn't%20change%20anything...%20just%20redone%20the%20IF%20and%20copied%20the%20inside%20as%20is!%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We use Office 365. We have a workflow (SharePoint 2010) that sets permission for a list item. It fails since June 29th. Anyone else has issue with workflows recently? 

I don't have much details about the error. Only a correlation ID and still waiting for Microsoft to give me the detail of the error :(

1 Reply
Highlighted

I wasn't able to get the error associated with this correllation ID from the Microsoft.com support. Apparently some people here can provide this information to me on a PM. That's what they said...

 

I fixed my issue by modifying my workflow... I redone an IF statement that was broken for unknown reason and now it work. I didn't change anything... just redone the IF and copied the inside as is!