Input box not performing workflow?

[asked111]

I noticed today that my input box is not triggering any workflows when pressing enter.

To try to get to the bottom of it, I’ve created a test page a single group containing only an input box and a “go” button. That’s it.

The button workflow simply pops up a message saying “done” - but that never happens.

“Prevent Enter From Submitting” is OFF.

I’ve tested on different browsers too.

What am i doing wrong? or is this a recent bug?

[carlovsk.edits]

Does there need to be any action inside that uses the value from your input. Is the workflow set up like this?

Look at this example: I have an input and a button, and inside the button’s workflow I create an item, where the item’s field uses the value from the input.
That way, the Enter key works perfectly.

[connect10]

@asked111

I noticed today that my input box is not triggering any workflows when pressing enter.

To try to get to the bottom of it, I’ve created a test page a single group containing only an input box and a “go” button. That’s it.

The button workflow simply pops up a message saying “done” - but that never happens.

“Prevent Enter From Submitting” is OFF.

I’ve tested on different browsers too.

What am i doing wrong? or is this a recent bug?

Hey! @asked111 If your workflow isn’t triggering when pressing Enter, a few things to check:

First, Bubble doesn’t automatically run a workflow on Enter unless you use the “When input’s value is changed” event or a “Detect Enter” workflow. Turning off “Prevent Enter From Submitting” only prevents the page from submitting a form, it doesn’t trigger a workflow by itself.

The easiest way is to either:

• Use a button and have the user click it (works reliably), or
• Use a workflow event for “Input’s value is changed” and add a condition to detect Enter (you can use This Input’s value:extract with Regex if needed).

It’s not a bug, it’s just how Bubble handles Enter key events differently from clicks. Hope this helps.

[alex.krajcar]

Hi mate, I just started having this same problem today on workflows which were previously working fine.

Not sure what the fix is yet, let me know if you find the solution.

[asked111]

Thanks @carlovsk.edits that was the reason - it needed the associated workflow to directly reference the input boxes value! As i don’t need to ‘create’ anything i’ve simply used a dummy state, which also works. Thanks again!

@connect10 I think your answer was a Ai response that is inaccurate and confusing. I’ve seen a number of Ai replies here recently that are inaccurate so i suggest you delete it as it will likely confuse new users or reinforce the ai’s training on wrong information.

[carlovsk.edits]

@asked111

Thanks @carlovsk.edits that was the reason — it needed the associated workflow to directly reference the input box’s value! Since I don’t need to “create” anything, I’ve simply used a dummy state, which also works. Thanks again!

Great! A lot of the time I use a custom event with certain actions that aren’t necessarily a create action, so I add a parameter to it to receive the input value. Then, on the button, I trigger the custom event and pass the input value into the custom event’s parameter, and it works that way as well.

@asked111

@connect10 I think your answer was an AI response that is inaccurate and confusing. I’ve seen a number of AI replies here recently that are inaccurate, so I suggest you delete it, as it will likely confuse new users or reinforce the AI’s training with incorrect information.

I don’t know if it was an AI-generated response, but I really do see many that seem to be, and that’s bad for the community