cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Sharepoint file size returned as zero bytes

I have a flow which is used to log incoming files from customers;

  1. File is uploaded to sharepoint document library.
  2. Item is created in sharepoint list to log the file, who uploaded it and when and also a number of decisions made throughout the remainder of the flow.
  3. File is attached to list item and deleted from library.

There is a file size limit for attachments to list items so I need to check the size before i try to attach to avoid an error and the rest of the flow failing;

  1. Send an HTTP request to SharePoint.
  2. Get file metadata.

Both of these methods sometimes return zero bytes for the file size and therefore my flow fails.

Is this a bug?

1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

I've now done some testing, using "Get file metadata" at 0, 10 and 60 minute intervals, uploading files ranging from 100Kb to 150Mb.

It seems that there is an issue if you try to get the file size in the action immediately following the trigger. I would have thought that the trigger would not start until the file upload was complete but this suggests that something is not quite finished when the trigger happens.

So, the result is I'm adding a 10 minute delay after the trigger on all my flows. Not a great solution but will do as a workaround for now.

Hopefully anyone reading this will be helped by what I've found, and Microsoft will investigate.

View solution in original post

3 REPLIES 3
v-bacao-msft
Community Support
Community Support

 

Hi @Anonymous ,

 

Have you checked if the source file is empty?

Please share screenshots of your Flow configuration for further analysis.

 

In addition, you could consider adding a Delay action on top of the Get File content or Add attachment action and then delay these actions for 1-2 minutes.

Please take a try and see if it helps.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

Here is the output of "Get file metadata" which shows the file size as zero;

 

Get file metadata.JPG

 

And the resulting zero is written to the variable, as you would expect;

 

Initialise FileSize variable.JPG

 

But when the file is copied from it's original location to another library the file size is correct;

 

Copy file.JPG

 

When I check the original file it is not corrupt and has the expected non-zero file size.

 

This problem is intermittent and does not seem to be related to how large the file is or what type of file.

Anonymous
Not applicable

I've now done some testing, using "Get file metadata" at 0, 10 and 60 minute intervals, uploading files ranging from 100Kb to 150Mb.

It seems that there is an issue if you try to get the file size in the action immediately following the trigger. I would have thought that the trigger would not start until the file upload was complete but this suggests that something is not quite finished when the trigger happens.

So, the result is I'm adding a 10 minute delay after the trigger on all my flows. Not a great solution but will do as a workaround for now.

Hopefully anyone reading this will be helped by what I've found, and Microsoft will investigate.

View solution in original post

Helpful resources

Announcements
MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

MBAS Attendee Badge

Claim Your Badge & Digital Swag!

Check out how to claim yours today!

secondImage

Are Your Ready?

Test your skills now with the Cloud Skill Challenge.

Top Solution Authors
Users online (47,418)