TIL 'reset' is buggy and runs multiple times when it shouldn't

It turns out that the reset action runs way too many times and causes too much havok. Just enabling it makes it run when the plugin first runs and then it runs anytime autobinding runs.

Anyone else ran into this issue? … knew about this?

1 Like

I haven’t used autobinding in a while, but I’ve never noticed this behaviour before. I have a few suggestions for you

  1. Double check your page workflows and make sure there’s nothing triggering a reset somewhere else unexpectedly. Use debug mode’s “Step by Step” to determine if indeed any reset actions are being triggered when you’re experiencing this issue
  2. In your initialize function, create a function called
instance.data.reset = () => {
 // reset actions here
}

and then create a new element action called “Reset”. Inside your new reset action, simply trigger the function instance.data.reset(). Now you can better control resetting your plugin and use the reset functionality elsewhere in your code.

1 Like

Thanks, checked it all. It fires as soon as the page loads. There is no Bubble workflow calling the reset.

I’ve submitted a bug report and its already been forwarded to their technical support team.

Let’s see.

Actually, I’ve submitted a bug report for the reset action a few weeks ago too.

Indeed, the reset action can be trigerred on page load, but also, there is no “reset input” element action available on workflows when a plugin input element is on the page. Only when a native Bubble input is there. So you don’t really know what trigger this action.

In the meantime, creating a custom action in your element is a way to do that without using the buggy “reset” native Bubble action.

Hope Bubble will make that more clear!

1 Like

For information I had a response from Bubble about this bug. They said that obviously it’s a bug but they don’t make the fix a priority.

So this is now a known bug, but no idea when it will be fixed.

In the meantime, the only option is to not use the option “Action on reset input”, but instead create a custom action doing the same thing, exactly like @jonah.deleseleuc example.

2 Likes