Nothing is shared
Work through this list:
- Is PressQueue in test mode? Then Activity shows test runs and nothing is sent. Choose "Live" under Settings, "Sharing mode". If it says "Paused", click "Resume sharing".
- Is a sharing rule switched on? Rules start off until you test them and turn them on.
- Is the channel on under Channels, and does the rule use it?
- Why was this post skipped? Open "Check a post" on the Overview, or the "Why posts were shared or skipped" tab in Activity. It names the reason, for example a "never share" rule, "Sharing off" for the post, or no matching rule.
- Is the post dated more than a day in the past? Then it is not shared automatically. Use "Share now" in the editor or Share old posts.
- Is the post private or password-protected? Those are never shared.
- Is opt-in sharing on? Then new posts start off. Switch "Share this post" on.
Shares stay in Waiting
PressQueue sends in the background through WordPress's scheduled tasks. WordPress runs them when someone visits the site. On a quiet site, or on a server that blocks these requests, shares wait.
The Overview warns you with "Background tasks have not started yet" or "Background tasks are running late". Open "How to fix it". Ask your host to run WordPress cron every five minutes, or add a cron job on the server with your own address:
*/5 * * * * curl -s https://example.com/wp-cron.php?doing_wp_cron >/dev/nullWith WP-CLI you can run the waiting tasks by hand: wp action-scheduler run.
If Settings, Data and privacy says "Background sharing is stopped.", read the reason there. This happens while PressQueue updates its database or when its stored settings are damaged, and the page says what to do. Shares wait until it runs again.
Buffer did not accept a share
A "Failed" share in Activity names the cause.
| What it says | What to do |
|---|---|
| "Buffer said the API key is no longer valid." | Create a new key in Buffer and paste it under Channels, "More", "Replace API key". |
| "Buffer refused access to this channel." or "Buffer could not find this channel." | Check that the channel is still connected in Buffer, then click "Refresh channels". |
| "Buffer rejected the post." | Check the message and image of the rule. Buffer may not accept this kind of post for this channel. |
| "Buffer limits requests per day." | Wait, then retry. |
| "PressQueue could not reach Buffer." | Your server could not reach api.buffer.com. Ask your host whether outgoing HTTPS connections are allowed. |
Then click "Retry".
A share says Check Buffer
Buffer's reply was unclear, so PressQueue waits for you to look in Buffer. See Check Buffer.
A post appeared twice
PressQueue never sends the same share twice by itself, and a share with an unclear reply waits under "Check Buffer". If a post appears twice, another plugin or service shares the same posts, or a "Check Buffer" share was retried without looking in Buffer first.
The key stopped working
The Channels page shows "Key no longer works" when Buffer no longer accepts the saved key, usually because it expired or was deleted in Buffer. Buffer keys last 30 days unless you pick a longer expiry. Paste a new key under "Paste a new API key". If you changed the security keys and salts in wp-config.php, use "Replace API key" instead. See Connect Buffer.
A channel is missing
Click "Refresh channels" after adding a social account in Buffer. PressQueue cannot post to Instagram, Pinterest, TikTok, YouTube or Google Business. Such channels show up as unsupported.
The message is too long
Each message, including the link, must fit within 280 characters on every network. The preview in the rule editor counts for you. Shorten the message or cut the excerpt with {{ excerpt | truncate:120 }}. See Messages.
No social image
Social images need the PHP GD extension with FreeType. The Social images page says "This server cannot draw images." when it is missing. Until your host turns it on, posts are shared with text and link. If a link preview shows another picture, check the "Link previews" setting and the image set for that post in your SEO plugin, which wins.
Where to get help
Report bugs and ask questions in the issues of the PressQueue repository on GitHub. For a security issue, use the repository's "Report a vulnerability" option instead of a public issue. When you report a problem, include the identifiers from "Technical details" in Activity. Never post your Buffer API key.