not Company

i'll need to check

Essentially my guess is timezone differences; I'm not exactly sure which timezone the Deployment

Start Time

is in, but I believe it's either server time or Company time

and the Execution Log times are definitely in your User Preference time

I check my User and Company Timezones and they are both in Pacific. Data center based on URL is na1 which I think is also Pacific server time

na1

is Eastern

so I suppose I would expect a 3-hour difference then

The start time is relative the user time zone.. so if you say like 12:00pm eastern, it'll run 12:00pm eastern but it'll be 9am server-side for example

this is how i've seen it work

But I should still see 12:00 am in the server logs right? Also for some reason I could not search for yesterday's logs

you'll see whatever the time it is for you when it ran

if you set it to run @ 12am then it may have queued up to run but didn't run until 230am as well

Depending on traffic on your multi-tenant system, i've seen scripts hang for hours before they start

^ ooo also that

thanks

CHALLENGE! Can you partially deposit a payment?

i’m a little shocked that there are fields in the xml data for a record that are inaccessible in SuiteScript and csv import. is it crazy if I create a custom field on record object and pre-populate it with its xml data? I don’t know how else I’m supposed to access fields that are in xml on-the-fly

Hello all, In an User Event Script I am creating a task that schedule a schedule script to be run. I am passing the internal id of the record from the user event script to the schedule script. In the schedule script I am loading the record using the internal id. I am getting and setting field in that record and at the end when I am saving the record I get an error message of , message: "{"type":"error.SuiteScriptError","name":"FAILED_TO_SUBMIT_JOB_REQUEST_1","message":"Failed to submit job request: INPROGRESS." I decide to call a schedule script to run the code because I didn't want to run into goverance issue. I was wondering if this is possible or I have to do my scripting in the User Event area. Thanks

Your User Event is triggering a Scheduled Script which modifies the same record which triggers your User Event which tries to schedule the Scheduled Script again

which fails because it's currently running

@Thai Your user event is trying to schedule the task when it is already running. You’ll either need to create a new deployment on the fly every time your UE fires (and clean them up within the scheduled script) or keep a crapload of deployments out there and don’t specifiy a deployment id when you fire your task.

You're essentially designing an infinite loop; only the error is preventing it

Oh, nice catch @erictgrubaugh that is probably also happening unless you’ve planned for avoiding firing your UE within your scheduled script.

Ah. Okay. @mattdahse is there a way to avoid firing my UE when I do the scheduled script?

You can check the context type.

which search is preferred while using in script creating search through UI or dynamically creating search

@aaz I've heard people theorise that "saved" saved searches may be more performant because NS can optimise them, but I have never seen anything official/conclusive

My take is if you need the search exclusively for a script, create dynamically. If you need the search for other purposes, for masses to see or for portlets or any other scenario where you want to visualize what you process, create a saved search.

Ultimately it's a matter of preference. A good use case for saving searches is if you want to allow non developers to make changes. I personally like keeping everything inside the script to keep customisations more contained (less of a concern with SDF..)