QuiboDocs
HomeSign in

articles

Scheduling

Calendar, drag and drop, batch approve.

Three ways to schedule

1. Per-article: open the article, pick a date and time under Schedule publish in the sidebar and click Schedule. The time must be in the future. Status flips to Scheduled. Unschedule in the Publish panel sends it back to Ready. On an article whose publish failed, it drops the date it kept and leaves the Publish failed mark in place. This works the same on a phone.

2. Calendar drag and drop: open Calendar. Scheduled articles appear as blue events and published ones green. An article whose publish failed stays on the day it was due as a red event marked Publish failed, and one waiting for an automatic retry is marked Retrying, or Checking your site when Quibo will first look for a post that may already be there. Drag a scheduled, Retrying or Publish failed event to another day or time to reschedule it. A Checking your site event stays where it is until the check is done. Click an event to open its editor. Published articles, and articles whose generation failed, cannot be moved; dragging one changes nothing. On a phone the calendar shows a list and events cannot be dragged: tap the article and pick a new date under Schedule publish.

3. Batch approve: useful when you want every article in a batch on a regular cadence. It is included on every plan and every lifetime tier, Free included.

  • Click Batch approve (N), where N is the number of Ready articles. If the calendar is filtered by site, N counts only that site and the batch schedules only that site's articles.
  • Pick when the first article goes out: a date and a time, in your own time zone, the one your browser reports. The dialog proposes the next available slot (today if the time is still at least 30 minutes away, otherwise tomorrow). Later articles keep the same time of day.
  • Set the days between publishing days (1 to 30, default 1) and the days of the week that may publish. Turn Saturday and Sunday off for a weekday-only blog; the cadence then counts only the days you left on, so "every 2 days, Monday to Friday" gives Monday, Wednesday, Friday, Tuesday, Thursday.
  • Set the articles per day (1 to 5, default 1). With more than one, choose the time of the last article of the day; the others spread evenly between the first and the last, snapped to a 5-minute grid and at least 15 minutes apart.
  • Read the preview: it shows how many articles are being scheduled, the first and the last slot, and the first few dates. If the start is less than 30 minutes away or the daily window is too short, the preview says so and the button stays off until you fix it.
  • Click Approve and schedule. Every Ready article in scope gets a slot, in order of last update with the oldest first. Two kinds of articles are left out, and the count on the button does not include them: an article whose post may already be on your site after a failed publish (see below), and an article whose publish failed before Quibo began marking failed publishes, because you may have published it on your site yourself since then. Check your site, then schedule each of them on its own page, or click Mark as published if the post is there. When the calendar is not filtered by site, the articles are dealt out across your sites in turn, so each site gets a steady flow instead of one site's articles all in a row. The confirmation message tells you the first and the last slot. Scheduling counts as your approval of each article, so the review trail records it.
  • Your cadence, weekdays, articles per day, start time and end time are remembered in this browser for the next batch. The start date is not: it is proposed fresh every time.

Ready articles do not show on the calendar until they are scheduled, except the ones whose publish failed: those stay on the day they were due. The count on the button tells you how many are waiting.

Behind the scenes

Quibo checks every 5 minutes for articles due to publish, up to 25 per run, and pushes them to your CMS. Each article publishes exactly once.

When a publish fails

  • Temporary problems are retried on WordPress, Ghost and Webflow, when they come before the post is saved. Your site's address could not be found, your site refused the connection, asked Quibo to slow down, or was down for maintenance. On WordPress, a cover image that could not be downloaded or uploaded is retried too, because the post is only created after the upload. Quibo tries again after 5 minutes, 15 minutes, 1 hour, 3 hours and 6 hours: six attempts in all, the last one about 10 hours after the scheduled time. Meanwhile the article stays Scheduled, marked Retrying on the calendar and on the Articles board, where its card shows the time of the next try. These three CMSs publish in one request, and Quibo retries only the failures that come before that request saved anything. On the other CMSs a second try could leave a second post behind, so the first error from the site is final, even when the site could not be reached. A temporary problem on Quibo's side, before it contacts your site, is retried the same way on every CMS. If you publish a Retrying article on your site yourself, click Mark as published on its page so the next try does not post it again.

  • Errors that would come back every time are not retried. A rotated password, a missing permission, a missing field or an upload refused by a security plugin fail the same way on every try, so Quibo stops at once.

  • When the post may already exist, Quibo checks your site before it tries again. If your site stops answering or does not answer in time after the article was sent, or answers with a server error that is not a maintenance page, the post may have been created anyway. Publishing again without a look could post it twice. On WordPress, Ghost and Webflow the article stays Scheduled, marked Checking your site on the calendar and on the Articles board, where its card shows the time of the next check. At least 5 minutes later, so a slow save can finish, Quibo reads your site for the post, unpublished, scheduled and private posts included. It looks for one whose address is the article's slug or that slug with "-2" to "-5" (WordPress and Ghost add these when a slug is taken), whose title is the article's title, and which was created after the article was due to publish (for Publish now, after you clicked), with 15 minutes of leeway for your site's clock. An older post with the same slug and title, or a post another article in Quibo already records, is never taken.

    • If the post is there, Quibo records the article as Published with the post's address, without posting it again. Nobody is emailed.
    • If your site answers and the post is not there, Quibo publishes the article at once.
    • If your site does not answer the check, or Quibo cannot run it, Quibo checks again at the next retry time (15 minutes, 1 hour, 3 hours and 6 hours later). Each check counts as one of the six attempts. If no check gets an answer by then, or your site refuses Quibo's login, Quibo stops and asks you to check your site first.

    On the other CMSs Quibo cannot look for the post, so it stops at once and asks you to check your site first. Batch approve leaves such an article out until you schedule it yourself.

While an article is Checking your site, Publish now on its page is off for a few minutes after the publish that may have created the post, so a slow save can finish first. The Publish panel says how long is left. After that, Publish now runs the check at once: it records the post if it is there, publishes the article if your site answers and the post is not there, and publishes nothing if your site does not answer or the check cannot run. Mark as published records a post you can already see. Schedule is refused until the check is done, because a new date would forget that the post may exist, and on a computer its calendar event cannot be dragged. Unschedule stops the checks and marks the article Publish failed, as a post that may be on your site.

On WordPress, Ghost and Webflow, Publish now works the same way on an article marked Publish failed whose post may already be on your site: it is off for a few minutes after the failure, then it looks for the post first and publishes the article only if your site answers and the post is not there. It takes a post with the article's slug and title made at any time after the article was written, so a post from an earlier try is found. Schedule does not look, so check your site before you pick a new date for such an article.

When Quibo stops, the article goes back to Ready and keeps its date. It shows in red as Publish failed on that date in the calendar and on its card on the Articles board, with a short reason. The card says Was due once the date has passed, and On hold for when the date is still ahead. It does not publish by itself. The organization owner gets an email that names the article, gives the reason and says what to do. The full error is on the article page.

To fix it:

  1. Correct the cause, for example reconnect the site in Sites or allow the upload in your security plugin.
  2. If Quibo says the post may already exist, check your site. If the post is there, do not publish or schedule the article again. Open the article and click Mark as published in the Publish panel, and paste the address of the post under Live URL. The address is optional, but Search Console stats and internal links need it, and it must be on your site's domain. The article moves to Published and the Publish failed mark goes. Do the same if you published the post on your site yourself. Until you mark it, the article does not publish by itself and Batch approve leaves it out. Unschedule takes it off the calendar and keeps the Publish failed mark. Like any failed publish you do not fix, Quibo removes the article 14 days after the failure, or 14 days after the date it kept if that date is later. The post on your site is not touched.
  3. Otherwise, open the article and click Publish now, or pick a new date under Schedule publish and click Schedule. On a computer you can also drag the red event to a new day. A new date clears the failure. Nothing is regenerated.

If you no longer want the article published, click Unschedule on its page to drop the date.

If Publish now fails on WordPress, Ghost or Webflow after the article was sent, so that the post may already exist, the article is not marked failed. It is scheduled for the time you clicked and marked Checking your site, a message says that your site did not confirm the publish, and Quibo checks your site a few minutes later as described above.

If Publish now fails in any other way on an article scheduled for a later date, it stays scheduled for that date when the failure left nothing on your site, and the error shows on its page. That is the case when Quibo failed before contacting your site, or on WordPress, Ghost and Webflow when the post was surely not created. Otherwise the article goes back to Ready, marked Publish failed, so a second try at the planned time cannot post it twice: on the other CMSs when the post may already exist, and whenever the error came from the site.

Time zones

Batch approve dates and times are read in your browser's time zone, and each slot keeps that local time even across daylight saving changes. The calendar shows times in your browser's time zone too. The notes about a failed publish, on the article page and in the email, give times in UTC.

What if I'm in vacation mode

Schedule the entire batch at once with batch approve. Walk away. Come back to a fully published month.

Calendar feed

The Subscribe to calendar feed card at the bottom of the calendar gives you an iCal URL for Google Calendar, Outlook or Apple Calendar, listing your scheduled and published articles. An article whose publish failed stays in the feed on its date, named "Publish failed".