Hi @infohouse25,
Can you share what your workflow looks like. Which object type is your workflow triggering on?
PS. If you’re not comfortable doing it in public you can get in touch over here: https://www.wundermatics.com/support/contact/
the workflow works when order is completed and have a specific product in order to change to processing that is working but when i want to change it to completed again the status change to processing that means the function run once per order is not working
-
This reply was modified 5 years, 2 months ago by
infohouse25.
Hi,
Thanks for reporting this.
We’re aiming to release a bugfix update within a few days, we have a few issues sorted in cooperation with other users. As with them, we’ll try our best to replicate your issue in our test environment based on your input and have a fix in the next release.
If you want to contribute to our efforts to with additional details, screenshots etc. you’re more than welcome!
Hi,
Update. We’ve just released 1.6.3 that has a fix for the runonce issue. We’d be very interested in hearing your feedback on the new version. Either here in the .org forum or on our support page:
https://www.wundermatics.com/support/contact/
Hello again the problem remains is not fixed
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?
Hello again i updated the plugin to the latest version, the runconce is not working i disabled – enabled the plugin , i saved the workflow with disabled runonce and i enabled after again but the same problem if there is any way to post the metadatas to help you tell me
workflow: order completed
order products [order] contains any “itemnumber_test”
action change status
object order
set new processing
