Netsuite Sync Error (Queueable jobs limit exceeded.NetSuite Flow Id:null,GUID:null,Connector Id:null,Cause:null )
Our Salesforce instance is receiving an error associated with some accounts stating: Queueable jobs limit exceeded.NetSuite Flow Id:null,GUID:null,Connector Id:null,Cause:null. This does not seem to have an impact with the account information transferring over to SF to NS, however both Celigo and SF have failed to associate the error to a singular incident. I am posting this to verify if anybody has potentially seen this error and if so is there resolution to this error.
1
Comments
I am seeing the same error on accounts in our salesforce instance. Were you able to find the reason/resolution for this?
I would also like to know, this happens often enough with Contact records after our Marketing automation I figured it's just too many contacts syncing at once, but today I got the error on a Salesforce Account, and these records are not created as often and there was only 1 error, not several accounts with the same error, so I'm wondering if it's hitting a concurrency elsewhere in Netsuite... Re-trying seems to do the trick, but I would like to know the root cause please.
Can you please help me with the flow name you are seeing this error? Are you using the V2 version or the IO? Also, it would be helpful if you provide when exactly you are seeing this error, Contact creation or Account creation or something else.
Thanks
Hey there Sushil,
We're on V2 for now, and this seems to happen upon Contact creation and the latest one happened on the account, but I already retried and resolved the error so I can't say if it was upon creation for 100% certainty.. If I get another error with this response I will be more diligent about documenting it (and I can open a ticket with support) so we can get to the bottom of this.
Thank you!
The error itself mentioned there is queueable job limit exceed, so we need to observe the queued messages in Netsuite
when the error occurs again, In Netsuite: type queued messages in global search and if you find any queued messages , it might be the reason for the error.
Please look out for another instance for the error and we can use it to find the root cause.
Thanks!
Please sign in to leave a comment.