Hey @redvivi, just confirming, this 4.5MB limit is still applicable right? Is it a Bubble limit?
Only for backend operations yes & yes.
You may find this plugin useful:
1 Like
Evening. I’m looking to change my workflows so that my users can upload multiple images at once. These are my workflows…
Can someone tell me what I need to change in order to continue these steps for each file uploaded.
Thanks in advance 
1 Like
@lisaalger In your “All Files Uploaded” event, Steps 2 through 6 should be moved to a “WasabiDropzone A Uploaded File Loop” Event
So for each file uploaded it will run your workflow you want. Any of the actions should reference This WasabiDropzone's Latest Uploaded File's [field]
And the Dropzone element should have the “Upload Multiple Files” checked and probably Retain Folder Structure" unchecked
Then you could have a “When condition is true” (set to Everytime) event with the condition WasabiDropzone A's Accepted Files:count > 0 and do “Show Elegant Loading”
In your “Accepted file loop” event, probably Step 1 and 4 can go away since it will show the loader at the beginning, then hide it at the end of all files being uploaded.
So your “All Files Uploaded” event should really just have “Reset Dropzone” and “Hide Elegant loading”
Also what are you using “Get File Metadata from Wasabi” for? It only returns size which already is available from the WasabiDropzone element This WasabiDropzone's Latest Uploaded File's file_size_bytes
Once again, you are a legend 
thank you @tylerboodman
1 Like
Multi upload working, thank you @tylerboodman
…but it’s only allowing 2 uploads at a time. Any thing more it show this:
It then uploads two of the uploads but not the rest
Hey @LA81638 !
I would suggest to refer to the demo editor for an implementation example, which you can find on the plugin page, Service Link.
I put it here for your convenience.
Cheers, will take a look. Popped on here though as it says to report to plugin author
For sure, however that’s likely an implementation mistake leading to that error.
@redvivi I’ve copied the steps and it’s still showing the error when it’s more than 2 files. I know it’s something I’m doing/implementation mistake, but hoping someone can help me as it’s not clear to me what’s causing this error.
Here’s the demo screenshots next to screenshots of my setup…I obviously have some extra steps, which I’ve included:
My extra steps:
If you could point me in the direction of what’s making this error occur after the second file is uploaded I’d be very grateful.
Many thanks
@lisaalger Please show the parameters of the Upload Current File of Dropzone in your Dropzone Accepted File Loop?
Also please confirm you are running the latest version of the plugin.
Lastly, please check in your application logs for any errors, including checking the values that are passed on each actions.
And yes re latest version installed:
Here’s the process with debug on: https://vimeo.com/875578524?share=copy
Thanks for looking at this. Know I’m obviously missing something but really struggling on this one
Ha! Got it!
You are resetting the Dropzone after the 1st file, so of course any files reference are gone for the 2nd file, so it will crash for any subsequent file.
The Dropzone should not be reset until all files processing are completed.
1 Like
Thank you @redvivi and sorry for taking up so much time! Sometimes I just can’t see the most obvious thing when adding in all the steps. Really appreciate your help
2 Likes
I have included a bucket name validation test, just in case 
. The issue should be more explicit now!
1 Like
Also @LA81638 I like to keep “Retain Folder Structure” off because if they upload a folder like Folder1/Folder2/file.ext it will actually upload like in that in your Wasabi bucket, vs putting the file exactly where you want it.
Like I like to bury each file in a subfolder with the file’s unique ID (available from the Dropzone’s Latest uploaded file), so every file is like
de24b2d5-1cc9-48d0-ad51-74a5659c1b48/file.ext
75dd2371-43a7-4b39-8ad0-7890310c8a09/file.ext
So I don’t want them to mess with the structure by letting them do
75dd2371-43a7-4b39-8ad0-7890310c8a09/Folder1/Folder2/file.ext
This also allows for duplicate filenames to be uploaded to the bucket, because each file is buried in a folder with unique name.
Not sure if right now you are just uploading all files to one giant folder
But just a suggestion 
1 Like
On this, I have the same issue for getting the download URL - user has to wait a while after the get download action runs to get the response. Is there anything I can do on my end to speed this up?
Yep that is the cold start on the SSA. I made a GC function to handle this instead and it is near instant
