Hi, I’ve run into the same issue before. From what I remember, switching to On leave or using a nanoflow solved it. If you still need server-side logic, you can trigger a microflow from the nanoflow, so the empty/null change is reliably handled. Did you try those workarounds?
Hi Jason,
Maybe not the best approach, but for this specific case you can try to catch it when the field is cleared by using one of these widgets:
Worth a try for catching the “empty” state.
Hope these widgets can handle it.
Was this when using an autofill from a browser, or when entering by hand?
I have had issues before with autofill not triggering events. My solution was to go into those fields manually for the event to trigger.