After rereading sean’s post, I still don’t see the workaround for triggering the value is changed event.
Here’s just a bit of a diagnostic page I have for testing this.
The top date(s) on the right are sourced from the picker’s value.
The second date down is a custom state that would be set in the workflow.
The third date is irrelevant for this discussion.
The only time the workflow ran and incremented the count is when I changed the date. Never when time alone was changed. (I think that is what sean was talking about.)
Interestingly, by the time I ran the debugger inspector, the picker’s value had the date shown, but it wasn’t reflected in the top numbers.