Is anyone familiar with using suitescript async ca...
# suitetalkapi
d
Is anyone familiar with using suitescript async calls and how to manage job performance?
To be specific, I am submitting 5 async update requests containing 150 records each...... However, when I view the monitoring page for these jobs it appears that only 1 is running. I am not sure how I achieve concurrency on these jobs.
b
i dont think thats how the async requests work
async for suitetalk means that requests are placed in a queue and are processed at a later time
netsuite returns a job id which your application should check to see if the job is done
in synchronous suitetalk, netsuite does the processing and returns the status of the job
d
@battk so there is no ability to achieve concurrency?
@battk just a FYI, after talking to a number of people (With NS and Consultants) SuiteTalk Async calls should behave exactly as I expected them to. In the case of my current instance we have 5 concurrent paths, the async jobs should run individually on any available concurrent path (Assuming your are making your calls by TBA)
b
were you able to make the asynchronous job queue process more than 1 job at a time?
you can submit multiple jobs into the queue but from what I've seen and what netsuite documents, the queue only processes 1 job at a time in the order received
d
No... apparently there is conflicting information within NS itself in regards to this topic
You are correct, even if I try using multiple app ids and tokens it will still only process one request from the async queue