Welcome to the Community @barryyeee! 

Thank you so much for bringing this to our attention. I did some checking and found that there was a bug report opened for these payload size errors just yesterday. So this appears to be an issue that’s only recently come about. I’ve added you to the list of folks being impacted by this issue which helps to increase it’s priority and will allow us to send you an email notification as soon as it’s been resolved.

There’s no reported workarounds at the moment but we’ll be sure to share any workarounds and/or updates here in this thread. 

Thanks again for flagging this, if there’s anything else I can assist with in the meantime please do let me know!

Hello Sam,

Thanks for adding me to the list. I received the email notification that told me the bug was solved :

We have made adjustments to optimize the data processing for this trigger. These changes ensure that the data payload remains within the allowable limits, allowing your Zap to stay active without encountering the previous error.

But when I tried to publish the Zap again it still failed with the same error. Should I re-create a new Zap instead of trying to re-publish the old one?

Thanks for letting me know, @barryyeee! Ah yes, I’ve just checked and can see that it’s been marked as solved. 

In order to take advantage of this fix you’d need to be running the latest version of the Amazon S3 app in your Zaps. Can you confirm whether your Zap is running the latest version?

If it’s not, please check out our Update to the latest app version in Zaps guide learn how to upgrade it.

Keen to ensure you’re all set here so please keep us in the loop on how you get on with that!

Hey Sam,

Just checked the app version and both Dropbox and Amazon S3 are the latest version. Also tried to create a new Zap but it doesn’t work. After I published it and a few minutes later I still can receive the same email saying “Your Zap could not be turned on” because of the payload size error.

Thanks for confirming that @barryyeee. Ah, I see what’s happened here! I added you to the bug report we had open for those errors that were occurring with the Amazon S3 app which should be resolved. However, looking again at your initial post it seems the error was coming from that Dropbox trigger, not Amazon S3.  I’m so sorry for the misunderstanding on my part there previously!

We’ve got a similar bug report open for these same “Response payload size exceeded maximum allowed payload size” errors with the Dropbox too so I’ve added you to that. Like before, I can’t provide an ETA on when it will be resolved by by we’ll send another email notification to you once it is. 

In the meantime, I did spot on the bug report that it was noted that setting the "Include file contents?" to “No” allowed resolved things for some users, so I’m wondering if you have that option enabled?

If so, can you try disabling it and let me know whether that then allows the Zap to be remain on? 

Hello Sam,

Thanks for updating and adding me to the bug report notification group. Unfortunately I cannot set Include file contents to No in my case. Anyway will keep eyes on the bugfix progress. Thanks for all helps again.

You are most welcome, @barryyeee. I’m sorry disabling the “Include file contents?” setting isn’t going to be a viable option for you.

If we come across any further workarounds or have any news on the status of the bug we’ll definitely share details of that here.

Hi @barryyeee! 

Just circling back in here to confirm that the bug report has been marked as solved as the Dropbox app on Zapier has upgraded and now supports larger payload sizes! 

I’m going to close this topic out now but if you’re still experiencing issues please do reach back out in the Community or get in touch with Support here. 

In the meantime, happy Zapping!