Hey!

You could use caching/database columns combined with failed() methods in your jobs for this. You‘d write the url of the current job into the cache or database table with the id of the job that‘s currently using it. When the job is done, you can remove the jobid from that column. If the job fails, you could also remove the jobid from it. You‘d also have to use retry or backOff for jobs so they can wait and/or retry if they fail.

If no api endpoint is available (all have a jobid set), let the job fail and remove the jobid from that api endpoint column. The retry/backOff will kick in and the job will be retried after the specified amount of time for the specified amount of retries.

To summarize:

• Create a new database table or cache item with api url and job id columns/array items.
• in the handle method of the jobs, query the cache to get an available api url (one that has no job id set) and store it inside a class variable (you need to update this in the failed method)
• in the failed method of the job you can remove the job id from the api url and by that release the api url and make it available to another job
• add retry variable and backOff method (you can also use the other methods of making the job retry itself)

I hope this is somehow understandable. Maybe someone else has an easier way of doing this or more experience with queues than I have.