:plus item adds an item, like most list operations it causes the list to discard duplicate items.
So to produce an end result of just (no), it would likely have tried to add (no) twice.
@romanmg I’m thinking it is a timing issue, Page Load might be triggering the workflow before the checkbox gets its checked status. Because if your suggestion is correct, the workflow is ignoring one of its own steps, which is of concern! Haha.
Edit - I tried it step by step, on the second step it shows the list as being empty, so I think @romanmg is partially correct …
step1 get the custom state value : empty list
step1 add the (yes) to the list
step1 set the custom state new value: (yes)
step2 get the custom state value : empty list hasn’t seen the new value from step 1.
step2 add the (no) to the list
step2 set the custom state new value: (no)
When I put a pause between the steps, the state goes from empty to (yes) to (no), which means either of:
The workflow can’t see updated custom states it has updated.
Or the pause is not preventing the step execution, just our seeing its result.
@rushabh can you explain how a list of (yes,no) is useful in your app?