Thread.Sleep in job scheduler

Sleeping for a second or less would likely not cause any problems, but I can't confirm 100%. An alternative would be setting your job to process that set number of calls, and setting its schedule to run every couple seconds.

Sleeping for a second or less would likely not cause any problems, but I can't confirm 100%. An alternative would be setting your job to process that set number of calls, and setting its schedule to run every couple seconds.

Yes, that can work.  The job executed calls against a third party web service which has a throttle on the # of calls I can make per second.  So if I do like you say and run it every :15 that should work just fine.