double transition to the status in the results of a complete break in warehouse operations and finances (if you do not solve such a bug, you can remove the prefix ERP)
double transition to the status in the results of a complete break in warehouse operations and finances (if you do not solve such a bug, you can remove the prefix ERP)
I have written about this issue before.
https://crm-onebox.com/en/support/business-processes/4754-povtorenie-problemi-perehoda-v-odin-i-tot-zhe-status-2-raza/
https://crm-onebox.com/en/support/stock/7423-bag---sistema-tovar-otgruzila-no-ne-snyala-s-rezerva-v-rezultate-ostatki-ne-pravilno/
I also see other users wrote https://crm-onebox.com/ru/support/business-processes/1977-ispravit-oshibku-dvoynogo-perehoda/
Here again I found the problem
In progress https://baza.cn.ua/admin/customorder/order/48166/edit/
The system was transferred to the same stage twice
See the story "Viconano → Turn the goods to the warehouse → Turn the goods to the warehouse → Turn the costi"
That is, twice transferred to the stage "Turn the goods to the warehouse"
Please see why the system makes such a gross error and correct
As a result, there is some kind of nonsense in the remnants and breaks
Here is the product https://baza.cn.ua/admin/shop/products/62600/storage/
Show that there are 2 retu
1. Previously, this problem occurs due to the bug inside mysql itself, but they solved it and those clients that have updated seem to not have it already 2. Also, as far as I can see, without waiting for the switch (working out the actions) - after 30 seconds you went to the stage again - right? we already have feedback from some customers that they no longer experience this after the update
1. Previously, this problem occurs due to the bug inside mysql itself, but they solved it and those clients that have updated seem to not have it already
2. Also, as far as I can see, without waiting for the switch (working out the actions) - after 30 seconds you went to the stage again - right?
we already have feedback from some customers that they no longer experience this after the update
Ustimenko Igor OneBox production wrote: 1. Previously, this problem occurs due to the bug inside mysql itself, but they solved it and those clients that have updated seem to not have it already
You corrected me something in the database, but as I understand it, it didn’t help
Ustimenko Igor OneBox production wrote: 2. Also, as far as I can see, without waiting for the switch (working out the actions) - after 30 seconds you went to the stage again - right?
It seems not, I waited a long time (moreover, there were more than 2 attempts to wait)
[quote]
Ustimenko Igor
OneBox production wrote:
1. Previously, this problem occurs due to the bug inside mysql itself, but they solved it and those clients that have updated seem to not have it already
[/quote]
You corrected me something in the database, but as I understand it, it didn’t help
[quote]
Ustimenko Igor
OneBox production wrote:
2. Also, as far as I can see, without waiting for the switch (working out the actions) - after 30 seconds you went to the stage again - right?
[/quote]
It seems not, I waited a long time (moreover, there were more than 2 attempts to wait)
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Donate
You don't have enough funds in your account Top up