Feel free to berate me for not doing enough resear...
# suitescriptc
Corey Schwoebel
05/26/2021, 5:59 PMFeel free to berate me for not doing enough research first. Busy day.
I have a scheduled script that's triggered by submitting a task from a UE script. My problem is that the user can be a bit fast, and cause a second task to be sent while the script is still in progress.
What's the workaround for this?
b
battk
05/26/2021, 6:03 PMwhat do you want to happen?
c
CD
05/26/2021, 6:03 PMWhat do you mean by "be a bit fast"? Updating the record again before the UE is done creating the task, so you get 2?
c
Corey Schwoebel
05/26/2021, 6:03 PMIs there a way to queue the second task up rather than erroring out?
b
battk
05/26/2021, 6:04 PMmake a second deployment
battk
05/26/2021, 6:04 PMschedule that one instead, or leave out the deploymentId parameter and let netsuite decide which one to use
c
Corey Schwoebel
05/26/2021, 6:06 PMI was hoping there was a better answer, but i've had to resort to something similar before. Leaving out the deployment parameter isn't something I considered, thanks for that.
b
battk
05/26/2021, 6:07 PMwhatever netsuite uses to determine if the script is already in the processor queue isnt thread safe
battk
05/26/2021, 6:08 PMit can still end up choosing a queued deployment at high levels of concurrency
c
Corey Schwoebel
05/26/2021, 6:14 PMI appreciate the info