Input elements with masking applied — such as decimal, currency, or date formats — use a third-party library that intercepts click events. This prevents clicks on the masked input from propagating up to any parent group that has an "element is clicked" workflow attached.
What you might notice
Clicking a masked input (e.g. a decimal or currency field) doesn't trigger a click workflow on a parent group
The same click workflow fires correctly when triggered by unmasked inputs or other elements
Workaround
Use a different trigger that works correctly with masked inputs. The "Input value is changed" event and "Do when condition is true" (with a condition based on whether the input's value is valid or not) are reliable alternatives to relying on a click event from a parent group.