Flow with multiple approvals stopped working

%3CLINGO-SUB%20id%3D%22lingo-sub-266951%22%20slang%3D%22en-US%22%3EFlow%20with%20multiple%20approvals%20stopped%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266951%22%20slang%3D%22en-US%22%3E%3CP%3EI%20created%20a%20flow%20for%20a%20sharepoint%20document%20library.%20A%20document%20could%20require%20review%20and%20approval%20from%20anywhere%20from%201%20to%2010%20approvers.%20So%20the%20library%20has%2010%20columns%20where%20the%20user%20can%20enter%20up%20to%2010%20approvers%20(Approver1%2C%20Approver2%2C%20etc).%20The%20flow%20creates%20an%20approval%20task%20for%20each%20approver%20listed.%20If%20approver1%20and%20approver2%20are%20filled%20out%20and%20the%20others%20are%20left%20blank%2C%20only%202%20approvers%20are%20required%20and%20only%202%20tasks%20are%20created.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20was%20working%20magically%20up%20until%20today.%20Suddenly%2C%20Flow%20does%20not%20like%20when%20there%20are%20Approver%20columns%20left%20blank%20and%20returns%20this%20message%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EBadRequest%3C%2FSTRONG%3E%3CSPAN%3E.%26nbsp%3BThe%20request%20failed.%20Error%20code%3A%20'InvalidRequestContent'.%20Error%20Message%3A%20'The%20request%20content%20was%20invalid%20and%20could%20not%20be%20deserialized%3A%20'Required%20property%20'assignedTo'%20expects%20a%20value%20but%20got%20null.%20Path%20''%2C%20line%201%2C%20position%201437.'.'.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAny%20ideas%20why%20this%20was%20working%20yesterday%20and%20then%20stopped%20working%3F%20Possible%20change%20to%20Flow%20(we're%20online)%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-266951%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-267149%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20with%20multiple%20approvals%20stopped%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-267149%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20your%20suggestion.%20I%20wish%20it%20were%20as%20simple%20as%20that.%20I%20double-checked%20and%20no%20fields%20are%20set%20as%20%22required%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20approval%20workflow%20suddenly%20just%20does%20not%20like%20it%20if%20an%20approver%20field%20is%20left%20blank.%20Again%2C%20this%20worked%20just%20fine%20yesterday%20on%20two%20separate%20libraries%20and%20works%20on%20neither%20today.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-267101%22%20slang%3D%22en-US%22%3ERe%3A%20Flow%20with%20multiple%20approvals%20stopped%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-267101%22%20slang%3D%22en-US%22%3ESounds%20like%20someone%20went%20to%20your%20SharePoint%20list%20and%20made%20one%20of%20the%20columns%20required.%20I'd%20start%20there%20and%20make%20sure%20that%20isn't%20the%20case.%3C%2FLINGO-BODY%3E
New Contributor

I created a flow for a sharepoint document library. A document could require review and approval from anywhere from 1 to 10 approvers. So the library has 10 columns where the user can enter up to 10 approvers (Approver1, Approver2, etc). The flow creates an approval task for each approver listed. If approver1 and approver2 are filled out and the others are left blank, only 2 approvers are required and only 2 tasks are created.

 

This was working magically up until today. Suddenly, Flow does not like when there are Approver columns left blank and returns this message:

 

BadRequest. The request failed. Error code: 'InvalidRequestContent'. Error Message: 'The request content was invalid and could not be deserialized: 'Required property 'assignedTo' expects a value but got null. Path '', line 1, position 1437.'.'.

 

Any ideas why this was working yesterday and then stopped working? Possible change to Flow (we're online)?

2 Replies
Sounds like someone went to your SharePoint list and made one of the columns required. I'd start there and make sure that isn't the case.

Thank you for your suggestion. I wish it were as simple as that. I double-checked and no fields are set as "required".

 

The approval workflow suddenly just does not like it if an approver field is left blank. Again, this worked just fine yesterday on two separate libraries and works on neither today.