hi,
i want to update aws file upload plugin from 1.196 to latest version. here i am confused like how to update in one go. right now if i select latest version it says on my app missing element, do i have to manually change each element ? if so that is troublesome cause my app is tasked based app and each task contains avg about 5 to 10 uploader and we have like 50 or so tasks and with conditional set with uploader so i did not understand how to update.
Hi there @nikmightynik ! 
Thanks for the detailed context - totally get why this could be confusing.
Short answer: when Bubble shows “missing element” after updating the AWS File uploader – Any size plugin, it means a major version introduced a new/renamed element (breaking change). In those cases, Bubble can’t auto-migrate existing instances, so yes - the affected elements need to be replaced. There isn’t a one-click global migration in Bubble for plugin elements.
What we recommend (safe migration plan)
-
Pause and review the Changelog
Open the plugin docs → Changelog. Any entries marked “breaking,” “element renamed,” or “props deprecated” indicate that older element instances will become “missing” after the update.
https://docs.zeroqode.com/plugins/aws-file-uploader-plugin -
Work in a copy / dev version
Keep production pinned on 1.196 while you migrate in version-test (or a duplicate app) so your live users aren’t impacted. -
Locate all affected places quickly
Use App search → search for “Missing element” to jump through every instance across pages. - Replace one page first, then replicate
- Add the new uploader element (latest) next to one of the “missing” ones.
- Re-map properties: bucket/region/keys (or the dynamic expressions you already use), file limits, multi/single, auto-upload, allowed MIME, etc.
- Recreate conditions that the old element had.
- Update workflows that referenced the old element (e.g., Start/Upload, Reset, Remove file, reading states like uploaded URLs). These will point to the old element’s ID; you’ll need to reselect the new element in each action.
- Once this page works, copy/paste that new element to other pages and adjust bindings. This is usually faster than configuring from scratch each time.
- Regression checklist
- Dynamic expressions still resolve (privacy rules / option sets / custom states intact).
- Any CORS/S3 policy you rely on hasn’t changed.
- “When upload is complete” events still trigger downstream flows.
- Test in debug_mode=true on version-test before pushing live.
Can you avoid manual work entirely?
For major element renames/structural changes (as noted in the Changelog), Bubble doesn’t provide an automatic, app-wide element migration. The best you can do is accelerate with App search, copy/paste of a “good” configured element, and a page-by-page sweep of workflows/conditions.
If staying on 1.196 for a bit is safer while you plan the switch, that’s perfectly fine - just keep production pinned and migrate a dev branch first.
Let us know if you encounter any issues while trying the suggestion mentioned above, and we’ll help you get through this smoothly.
Best regards,
Support Team
Browse all Zeroqode Plugins for bubble
okay, when will the older version stopped working ?
Hi again @nikmightynik !
There’s no scheduled sunset for your pinned version 1.196. In Bubble, a plugin version you’ve selected keeps running in your app until you choose to upgrade.
Keep in mind: older versions aren’t actively maintained. If external factors change (Bubble/runtime, browsers, AWS/S3 policies), 1.196 could eventually break and we wouldn’t back-port fixes - new fixes/features ship only to the latest versions.
Practical path:
- Keep live on 1.196 and migrate in version-test.
- Plan the upgrade on your timeline rather than waiting for a forced change.
Please go ahead and try the migration when convenient; if any issues pop up, we’ll be happy to help.
Regards,
Support Team
Browse all Zeroqode Plugins for bubble