I would try scripting the refresh using tabcmd then using the "--synchronous" command to force the extract refresh immediately, as soon as the backgrounder becomes available. For more info see:
That's a good solution, Diego--nice! I didn't even think of that one.
My only thought was to create separate Schedules, one set for each Project ("Project 1 - Hourly", "Project 2 - Hourly", "Project 1 - Daily", "Project 2 - Daily"). Then set each of those schedules to execute serially rather than in parallel--so each will use only a single Backgrounder at a time when it runs.
That strategy will work, but it can become a pain if you are growing, as you would need to:
- Create a whole new set of schedules for each new Project that is created
- Move content from one Schedule to another as more stuff is published up (unless your Publishers are very good at following Admin instructions -- just kidding, publishers like that don't exist! )