Hi there, can I pick someone's brain on the following? I'm working with an API has has very strict throttling limits. Even after batching requests, I'm still hitting the limits so I need a reliable way to add delays between calls without compromising performance (i.e. delays needs to be no longer than necessary). The solutions I've investigated/come across so far: 1. Use a 3rd party solution like EasyTimer.js: Errors due to dependencies not accessible on server-side. 2. Try to run a complex search to simulate the passing of time: (1) Imprecise (2) The query could always get indexed at some point and no longer run so slowly. 3. Call an API out there like Slowwly that produces a delay: Service might get discontinued without notice (incidentally, the site was down just now which proves the point). 4. Create my own delay service on AWS or elsewhere: Most attractive at this point but feels like an extra burden for something so "basic". Does anyone have another idea? Thanks.

choice 4 would be my favored solution

I created a super simply delay endpoint (using heroku). It takes a parameter called

delay

(in milliseconds). executes a 200 response using the

setTimeout

function.

@darrenhillconsulting Is your solution publicly available and guaranteed to stay in the air? Basically, can I use it for the foreseeable future?

Hmmm. Never considered allowing public usage. Let me ponder on that. I'd just want to ensure I'm not spending large $$$/monthly when doing that

Looking at heroku's free offering seems decent enough. That should be good enough

I also vote for #4. And the implementation would be so trivial I don't see the need for using an existing service. Indeed I would expect deployment/monitoring of said service is a lot more work than writing it. I also noticed that Slowwly seems to want to call out to somewhere else (adding a delay) - which isn't what you're asking for? Just a service that creates a configurable delay should be like a single line of code?

Hi @darrenhillconsulting, you're the best! Yes this is excellent. And since it's from you, I can trust that it will be in the air forever (no pressure). 😉 Enqueued for a future blog post on NetSuiteInsights as promised.

Ya, we use it for our own solutions ... so, its not going anywhere

@stalbert You're right slowwly does more but all I need is a delay so Darren's solution is perfect.

yes, darren's is better 🙂

@darrenhillconsulting Thanks once again. As promised, I've published an article on this: https://netsuite.smash-ict.com/2021/03/learn-how-to-create-a-netsuite-server-side-script-sleep-delay/

Thank you @netsuite_insights!