Custom state for button disabling not fast enough

I have a button and this button creates a thing in the database.
I dont want the button to create multiple things in case its clicked double, so I use a custom state that serves to disable the button via a condition after its clicked (i.e. if custom state X is “yes”, button cannot be clicked).

It seems that when the workflow starts, the setting of the custom state does not work fast enough, because when I do fast double clicking, the button still creates 2 things.

Does anyone know how to fix this? I want to button fail proof.

Hi there,

Here’s an idea that may work instead of using a custom state:

Instead of setting a custom state, what if you instead added a step in the workflow that when the button is pressed, the button is not visible/collapses. Have another identical button with your ‘not clickable’ formatting applied that becomes visible when the prior button is not visible so it’ll feel seemless to your users.

1 Like