The order number is duplicated when assigning the variable workflow.number - the serial number of the order

add another process id and this problem will not be, and it’s not a problem in general, as it were the bottom line is that until the process is fully saved in the database, the number is not considered unique, so when you have a bunch of actions and operations set up at stages and the switch takes a few seconds, you will continue to stumble upon this so my advice to you is to add id

Good day. For me, this is a critical issue. The process ID is too long and not convenient to use. Cool action to generate a unique number. Igor, let's come up with the same cool implementation. After all, for sure, you can change the logic so that the same unique numbers are not generated.

[quote] Ustimenko Igor OneBox production wrote: add another process id and this problem will not be, and it’s not a problem in general, as it were the bottom line is that until the process is fully saved in the database, the number is not considered unique, so when you have a bunch of actions and operations set up at stages and the switch takes a few seconds, you will continue to stumble upon this so my advice to you is to add id [/quote] Igor, please find a solution. Ready for paid revision

[quote] Ptashkin Sergey wrote: Good day. For me, this is a critical issue. The process ID is too long and not convenient to use. Cool action to generate a unique number. Igor, let's come up with the same cool implementation. After all, for sure, you can change the logic so that the same unique numbers are not generated. [/quote] yes, this is a great solution: Go to Onebox OS and increase server capacity there, data processing is accelerated at times - so the chance of getting into a simultaneous operation is almost zero

Thank you. We will definitely use. But this method improves, but does not completely solve the problem. The process ID is not set for you. So you can come up with the generation of a unique code from a template.

Igor, but is it really impossible to make a normal generation of a UNIQUE number? Even if it is impossible - write about it directly and close the topic.

[quote] Ptashkin Sergey wrote: Igor, but is it really impossible to make a normal generation of a UNIQUE number? Even if it is impossible - write about it directly and close the topic. [/quote] I answered above you have options either use id or switch to OS

[quote] Ptashkin Sergey wrote: The task is to generate a unique number. Use id - not suitable. And this is not a solution Using the OS does not solve the problem, but reduces the likelihood, but does not eliminate it. So there is no answer above. If you wrote "the task is not solvable, look for alternatives." I wouldn't ask 10 more questions. And it turns out that your "sequence number generation" action is buggy, but in your answers I hear that everything is correct in Boxing, I'm a fool. Sorry Igor. We can check the uniqueness in the next step with the action "Check for the presence of the value of the additional field of the current process in other processes" and throw an error in case of a double. Maybe you can modify it so that in the case of a double, re-generate the value? And, by chance, if for the additional field in which we generate a unique number, enable the setting "only unique values" - will this not help us? [/quote] no it won't help you if you are not satisfied with the id, then you can modify the current time variable in milliseconds or any other unique identifier

Thanks Igor. So far, we have stopped at checking the uniqueness, and if there is a process with the same number, we will generate it again. This method does not completely eliminate the possibility of a double, but reduces it significantly. We are watching.