Great question!

While we can set a Satellite to process Jobs from multiple Campaigns by enabling the “This Satellite processes Jobs in all Campaigns” option in the QUE Configuration window, there currently isn’t a mechanism in place to allow a Satellite to process Jobs that aren’t assigned to it.

This mainly prevents two Satellites from trying to process the same Job at the same time, since an unfortunately timed pull request could result in both systems having the same data simultaneously.

To get around this limitation, we’ll want to add a “bot” value to the Job with the Satellite ID of the system we want to process the data.

As a quick side note, if we’re using Zapier and don’t need the setup to be maximally responsive, we could add a “Code by Zapier” step before the Insert Job step and use it to run a script that cycles through several hardcoded Satellite IDs for the bot key. This would force Jobs to alternate across Satellites, which would result in behavior similar to what you described.

I’m sure that once the Code for Zapier option is integrated, it will open up quite a bit of flexibility moving forward, but it could be a bit tricky to get set up initially. I’ve also passed this on as a feature request to our development team, so we’ll see if this is something that we can integrate directly into QUE at some point.

Let us know if you have any other questions, and, as always, feel free to reach out to us at support@dataclay.com if you have any other issues.

Thanks,

Jeff