Power Platform Community Forum Thread Details

Hi, I created a power automate to move old news posts to an archive news site. It was working around 1pm today, however, I am now getting the error message below for the SharePoint 'Move file' action. I made some minor changes to the flow since then, but I highly doubt that the small changes I made would cause this error since I've made the same changes before and it still worked. According to CoPilot, the error can happen when the system cannot find the file or folder it is trying to access. But I went to the same page the flow was trying to access and it loaded as expected.

Is there anything I can do to fix it, or do I need to open a ticket with MS?

Action 'Move_file_to_News_Archive_UAT_de_folder' failed: Object reference not set to an instance of an object. CallStack -- at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx) at Microsoft.SharePoint.Library.SPRequest.PutFile(String bstrUrl, StorePath spWebRelativeUrl, Object punkFile, Int64 cbFile, Object punkSPFileMgr, Object punkFFM, SPFileSaveParams sfsp, SPFileInfo& pFileProps, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, String& pEtagReturn, Byte& piLevel, Int32& pbIgnoredReqProps, Int32& pcNonLimitedPrincipals, UInt32& pWnsSubscriptionCount, Int32& piListBaseType, Int32& piListTemplateType) at Microsoft.SharePoint.FileStore.SavePipelineInitiator.Run(IBufferedChangeFactory bufferedChangeFactory, IBufferedChange bufferedChange, SPFile fileForExceptionInfo, SqlSession sqlSession, SPWeb web, ConciseFileStateInfo conciseFileStateInfo, ISavePipelineInitiatorOptions savePipelineInitiatorOptions) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.SharePoint.FileStore.SavePipelineInitiator.Run(IBufferedChangeFactory bufferedChangeFactory, IBufferedChange bufferedChange, SPFile fileForExceptionInfo, SqlSession sqlSession, SPWeb web, ConciseFileStateInfo conciseFileStateInfo, ISavePipelineInitiatorOptions savePipelineInitiatorOptions) at....

Categories:

Building flows

Hi @1815

If this is CoPilot, go to the history tab for the Agent.

Find the failed one, look at the steps, go through them, find the action (if you are either using a CoPilot specific flow, or a Flow), and open it up.

Go to the action and see what values were input for the actions in flow.

Validate that the actual path is correct.

Also, no need to explain that you dont think your little change didn't break it cause you changed it before, it just bloats the reading :-)

Share the flow details, the CoPilot details and actual used values, and that will help resolve.

Because its either a bad path, bad data bits, bad file name, or permissions.

That or its purely a system back end uggggg that will go away on its own :-(