I have an error in a Flow where I have a sequence of approvals for a file created in the new folder, and when it is approved in the first step it is moved to the approving folder and if it is rejected in another step it is moved to the folder rejected, if approved in all stages it will be moved to the Approved folder. but you are only moving the file after the first step, in any of the subsequent steps the following error is returned:
An item with the same key has already been added. CallStack -- at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Microsoft.SharePoint.Deployment.MetaInfoHandler.Add(MetaInfoProperty property)
at Microsoft.SharePoint.Deployment.FileSerializer.HandleMetaInfo(ExportObjectManager objectManager, SPWeb parentWeb, Object metaInfoObject, SerializationInfo info, Guid listID, Guid itemID, String itemETag)
at Microsoft.SharePoint.Deployment.FileSerializer.GetDataFromDataSet(Object obj, SerializationInfo info, StreamingContext context)
at Microsoft.SharePoint.Deployment.DeploymentSerializationSurrogate.GetObjectData(Object obj, SerializationInfo info, StreamingContext context)
at Microsoft.SharePoint.Deployment.XmlFormatter.SerializeObject(Object obj, ISerializationSurrogate surrogate, String elementName, Boolean bNeedEnvelope)
at Microsoft.SharePoint.Deployment.XmlFormatter.Serialize(Stream serializationStream, Object topLevelObject)
Since yesterday I have the same problem with a similar flow. After the first step the file is moved without any problem, but in the last step is always returned the error "An item with the same key has already been added.......".
My flow worked without problem from january until yesterday, I cannot understand which is the problem, no changes in the flow have been made.
I have the same problem when moving files multiple times. We have three folders:
Ready for Internal QA
Ready for External QA
The flow always fails between Ready for External QA and Complete, and I get the same 400 error message.