Hello, a recent bug with the Google Drive Upload piece required us to update all pieces. Unfortunately, this update cleared our mapped inputs. Is there a workaround to persist the original inputs to the piece schema during updates? Remapping everything manually is time-consuming, so preserving them would greatly improve the user experience. Thanks.

Hi @Kel CAn you send us the flow link

@User Sure. We've updated most of our workflows to the latest version of the Google Drive 'Upload file' action, but here is a flow that still uses the older version: https://cloud.activepieces.com/projects/nsNY3Ao5hb0Q0wMOR1UU6/flows/XTDLZyJ1fd6HD3ujmBQsT It would most likely fail if you run a test.

just to be sure we understand correctly, you did go through these 2 steps when upgrading right ? you did this by clicking the green button then upgrading to most recent version. https://cdn.discordapp.com/attachments/1543939366437658645/1543964641418281001/image.png?ex=6a96c89f&is=6a95771f&hm=f97924d6360009c5e3f17b88d3d68f741caa90445298e4097cbc41c6e8878241& https://cdn.discordapp.com/attachments/1543939366437658645/1543964641749635137/image.png?ex=6a96c8a0&is=6a957720&hm=9d4daabd40a2b1c267eda3742c9e22f4b61d2f918e0359506cf53a2db0ad7fea&

@Abdul (Viva-Palestina)💔 yes that’s right. After updating, the action works as expected. The only problem is having to do this across 80+ workflows

@Kel for tracking purposes of this feature request, we can't provide you with an ETA on this, but Product team has been informed and will decide https://github.com/activepieces/activepieces/issues/15155