I released new version (0.2.2) It should be released in 5 minutes from now, I have removed filters as they were causing slowness and replacing the library please use branch piece as your filtration logic.
Loading test data should work and the trigger should be more reliable.
@karla If you already have flow published, you need to fix the settings and republish the flow again.
@benwhut Thank you for the credentials, I finally found it, there were an bug two network requests sent in parallel, the order of completion is not fixed that why it worked sometimes and sometimes not, I only could reproduce it with your imap credentials , It’s fixed now in 0.2.3 (should be out in 5 minutes)
I’ll try in a few moments, but just to let you know, that until 0.2.1 the emails were picked up twice, not sure if this is what you were just saying, and its fixed now.
@benwhut, it’s recommend to use the branch piece for better visibility and speed. It’s better not to add filters back for above reasons. Please let me know if you encounter any issues or have any questions.
One question about the branch piece: is it possible to do multi-branch routing, so instead of just 1 true/false option, can you do many? For example, if option 1, do x, if option 2, do y, if option3, do z, etc. I know this can be done with multiple true/false single branches, but it seems cumbersome and can get unnecessarily complex with 4 or 5 or more branches.