Pro The queue and scheduler are included in every PageForge Pro plan, starting with Starter.
Instant runs work through your data while the Generate screen is open. For large campaigns, or when you want pages to go live a few at a time, PageForge Pro can put rows in a queue that a scheduler works through in the background.
Turn on the scheduler
Open PageForge > Settings and set:
- Enable Daily Scheduler: processes queued rows with seven checks a day, in your site’s timezone as set under Settings > General.
- Daily Limit: how many pages may be successfully generated per day.
Rows that are skipped or fail do not count toward the daily limit. If a check finishes before the limit is reached and rows are still waiting, PageForge schedules follow-up runs until it is.
Queue a campaign
- On the Generate screen, choose the template and data source.
- Set Mode to Queue (Scheduler).
- Click Check and preview and review the result.
- Click Queue N rows for the scheduler.
The rows are added to the queue as one campaign. The Generation Campaigns panel on the Generate screen tracks it: Done counts resolved rows, Live counts published pages, Active counts rows still waiting, and Issues counts failed or skipped rows that need a look.
Drip publishing
Drip publishing spreads a campaign over time. Set the post status to Publish and choose a daily limit that suits you. With 200 rows queued and a limit of 10, the scheduler publishes up to 10 pages a day until the queue is empty, roughly 20 days.
A steady pace makes it easier to review pages as they go live and to catch a template problem before it reaches the whole campaign. It also lets you add internal links and hub pages as the set grows.
The Generation Queue screen
Open Queue in the PageForge navigation to see waiting rows:
- Edit changes a row’s values or post status before it runs.
- Run generates one row right away, without waiting for the scheduler.
- Process Next N Now runs the next group of queued rows right away. N matches your daily limit.
- Clear All empties the queue.
Removing rows, clearing the queue and cancelling a campaign need Editor-level access.
Retries and recovery
- Failed rows retry automatically, with a longer delay after each attempt, up to an attempt limit. The Failed and skipped rows list shows the reason, the number of attempts and when the next attempt is due. Retry now tries a row straight away.
- Skipped rows are not retried, because they cannot succeed as they are: a duplicate URL, a page edited by hand, or a page another template generated. Fix the row or template, then retry.
- Stalled rows are recovered. If a background run dies partway through a row, that row is returned to the queue after 15 minutes.
- Cancelling stops the campaign straight away. Its waiting rows are removed, and a run already in progress does not write cancelled rows back.
Who the rows run as
Queued rows run one at a time as the user who queued them. Background pages therefore get the same permissions and the same SEO title, description and social fields as an instant run. If that user account is deleted, its rows fail with a clear message in the failure list instead of creating pages without SEO fields.
Tip The scheduler runs on WordPress’s built-in cron, which fires when your site gets visits. On a quiet site, ask your host to trigger WordPress cron from a real server cron job so checks happen on time.
