
It's self-explanatory I guess. I'm parsing an email subject and allocating it to a particular inbox sub-folder then flagging it as unread such that the folder content gives the user a sense of how many emails are in there for followup.
The action block called Mark as read or unread (V3) gives three options being Yes, No or Enter custom value but none of these indicate mark as read or unread. Further inputting 'read' or 'unread' as a custom value throws an error as the action expects a boolean value.
Of course if this is designed as a toggle then that's ok, and potentially usable, however if the command was interpreted as 'Toggle between read or unread' and the answer was 'no' then why would I have the step in the first place? ie the only logical input for a step 'toggle between boolean states' is yes or skip the question and leave it as is, right?
Either way I've tried every manner available and no input makes any difference to the state of the email's read/unread status.
Anyone else encountered this?