Troubleshooting

Fixes for the problems people hit most often with BuddyPress Schedule Activity. If none of these resolve it, contact support at wbcomdesigns.com/support/.

The clock icon does not appear on the activity form

The scheduling control only loads for logged-in members, and the plugin only boots when BuddyPress or BuddyBoss is active.

• Make sure you are logged in. The icon is not shown to logged-out visitors.
• Confirm BuddyPress or BuddyBoss is active and the Activity component is enabled. If neither platform is active, the plugin deactivates itself and shows an admin notice.
• Check that you are on a page that actually has the activity post form (site-wide Activity, your profile, or a group you can post in).
• If a caching or asset-optimization plugin is combining scripts, clear its cache so the plugin’s JavaScript loads.

The Next button stays greyed out

Both the Date field and the Time field must have a value before the Next button becomes active. Fill in both, then click Next.

“Schedule time is in the past”

The date or time you selected has already passed in the site’s timezone. Choose a future date, or a later time today, and click Next again. Remember that times use the site’s timezone, not your device’s; see Scheduling an Activity for how to convert.

This warning also appears if you pick a date more than 90 days ahead, which is outside the allowed range.

“Security check failed.”

Your login session expired before the request was submitted. Refresh the page, log in again, and retry. This applies both to scheduling and to cancelling an update.

“Unable to schedule activity. You must be the group owner or a moderator to schedule activities.”

You do not have posting permission in that group, so scheduling there is blocked. You must be a group member with posting rights; on BuddyBoss the group’s own posting restriction (bp_group_is_user_allowed_posting()) is enforced. Ask the group administrator if you believe your permissions are wrong.

A scheduled update did not publish on time

Publishing is driven by a WordPress cron task that runs every minute, but WordPress cron (WP-Cron) only fires when someone visits the site. On a low-traffic site there can be a delay.

1. Wait a couple of minutes; cron may not have fired at the exact second.
2. Confirm the update is still in your Scheduled Posts list and its time has actually passed.
3. On a quiet site, set up a real server cron job so publishing does not depend on visitor traffic. See Cron and Publishing for the exact wp-config.php and crontab setup.

Site administrators can check the event with WP-CLI:

wp cron event list | grep buddypress_schedule_activity

Publishing appears stuck

The publisher takes a short-lived lock (the bpsa_publish_lock transient, 60-second TTL) so two cron runs cannot publish the same update twice. If a run is interrupted (server crash or PHP timeout) the lock can linger until it expires. It clears itself within 60 seconds, but an administrator can clear it manually:

wp transient delete bpsa_publish_lock

To capture publishing errors, enable debug logging in wp-config.php; the plugin logs messages prefixed with BPSA Cron Error: or BPSA Cron Warning::

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );

A newly published update does not show right away

A cached page may not reflect a just-published update. Refresh the page or clear your browser cache. Most caching plugins expire cached pages within a few minutes, after which it appears normally.

Cancel did not work / the update is still listed

Cancelling runs as a background request, so on a slow connection the list can take a moment to update.

• Refresh the page and check whether the update is actually gone.
• Make sure you are still logged in; a “There was a problem deleting your scheduled activity” message usually means the session expired. Log in again and retry.

Scheduled updates leak into the feed with rtMedia active

When rtMedia is installed, the way scheduled updates are hidden depends on rtMedia’s privacy setting, which the plugin detects automatically. If scheduled updates ever appear where they should not while rtMedia is active, confirm you are on a current plugin version and see Integrations for how the two hiding mechanisms work.

Still stuck?

1. Refresh and try again; many one-off errors clear on their own.
2. Try a different browser to rule out an extension or a stale cache.
3. Ask your site administrator about site-specific issues such as cron or caching.
4. Contact the support team at wbcomdesigns.com/support/.