Is there a way to lock a non custom record? So while 1 is processing, and another tries to access it, it holds until the other processess is completed?

Not that I know of. If you have 2 scripts load and submit a record, the one that submits first will succeed and the second one will fail since there were changes to the record since it was loaded

Yup, that's what happening. K, thanks

You can catch that error and try again

Do you know if there is a way to check and see if a record is processing?

non-custom records already do optimistic locking by default so if someone edits something that someone else has edited it'll error out. Trying to write your own locking mechanism is going to be a nightmare

look at using

_.attempt()

to help manage the potentially expected case of this error

k. I'd prefer it to be locked and error. Just need to implament a recursive call to handle this when they send in the same job back to back.

so you're trying to prevent duplicates more than a locking mechanism?

nah, because if it exists, i'm updating it. it's an AddOrUpdate type restlet

is there something unique that you can do a search on before you do anything

last modified date may be the only thing. I think what I can do is catch the "record been modified", pause a few seconds, then do a recurrsive call back to the same method.

you dont want your restlet to sit and spin though

Yeah, it'd only get 1 more try before exiting with the appropriate error

you can't 'sit and spin' - or at least NS doesn't provide a mechanism to do so, and you should run up against instruction count limits if you try a NOP loop

you certainly can sit and spin if you code it wrong