Hi @infohouse25 ,
Thanks for geting back to report this issue, even if it wasn’t the feedback we hoped for.
A bit of background:
The plugin uses meta data (a hidden custom field) on the post/order object to remember if that post/order had triggered that workflow id previously.
Before the upgraded version was installed, our plugin didn’t write the correct meta data to the affected post/order, so no “memory” of previous workflow execution would be written to the database.
After 1.6.3 was installed, the post meta field is correctly written to the database. But because of the bug, no memory of previous executions exists. So for any given post/order, a workflow with run-once will be effectively run one more time.
So just to clarify before we dive back into this issue:
When you say that you still see the same bug. Is it possible that you’re seeing the effect of “no memory” for an existing post or order. Or can you reliably reproduce the error for a new order and have a workflow run over and over again even if run-once is set?