new concurrency limits will affect this, read for details.

[hayden-t]

So in case you didnt know , Netsuite have cracked down on this connection method's ability to have up to 50 concurrent connections at one time, and for example ours is dropping down to 5 total for all methods combined. My work around for this has been to install a message queue with 5 workers and have all calls via this api routed via the queue.

[fastjames]

Hello @hayden-t thanks for this update (though it is sad to hear). I read through your other issue posts, and you are correct that it would be good to move collaboration to a fork. Acumen Brands ceased operations several years ago, and the current org admins on github (me) don't use Netsuite right now. I'm very happy that others have been able to get some value out of our work, and I would be glad to push a README update on this repo directing interested parties to a fork.

[hayden-t]

Well that sounds great and could be the thing to do. I recently found out the other active fork is operated by Tenfold, but they have all user interaction disabled there, so its a brick wall. https://github.com/callinize/rest_suite https://www.tenfold.com/support-center/netsuite-restlet , im currently in communication with their support team to find out how many concurrent connections they make at one time and what user account logins they use for a client. (our client uses them too by chance, so it was funny to go deploy the accumen scripts and find them there already.. so i just added my own modified copies) I do have my own fork running too if you look in pull requests. Had no idea Accumen was a company and that is was gone, so make sense why no response.

[hayden-t]

GovernanceChangesFAQ_PAGE1.pdf