Appearance
How to fix Revive Social not posting
If Revive Social does not share posts to social media for your website, then the issue might be with WordPress' Cron. This can be due to your website not having enough visitors or something is wrong with WordPress Cron, such as it being turned off without a replacement.
There are two ways to go about addressing this issue; the first one( Method 1) is the simplest, and the second(Method 2) involves creating a "True Cron" via your Cpanel account from your Web host.
If you are having trouble implementing Method 2, then please forward this document to your Web host support personnel. They will be able to implement the true cron for you. A recommended interval for the cron job would be once every 10 minutes.
Check whether any posts are eligible to be shared
Before troubleshooting WP-Cron, check whether Revive Social has any posts it can actually share.
Revive Social only queues posts that match your sharing filters from Revive Social > Dashboard > General Settings. If no posts match those filters, nothing will be shared even when your accounts are connected and your schedule is active.
How Minimum Post Age and Maximum Post Age work together
The Minimum Post Age and Maximum Post Age settings define one date window for eligible posts:
- Posts newer than your Minimum Post Age are skipped.
- Posts older than your Maximum Post Age are skipped.
For example, if Minimum Post Age is 1 day and Maximum Post Age is 4 days, Revive Social shares only posts published between 1 and 4 days ago. Newer and older posts are excluded.
Custom Schedule does not override eligibility settings
The Custom Schedule tab controls when Revive Social tries to share posts. It does not change which posts are eligible.
Even with a correct recurring or fixed schedule, Revive Social cannot post if no content matches your current age window and filters.
What to do if no posts match the age window
- Go to Revive Social > Dashboard > General Settings.
- Review your Minimum Post Age and Maximum Post Age values.
- Compare those values with the publish dates of your WordPress posts.
- Widen the age window (for example, lower Minimum Post Age or increase Maximum Post Age) so at least some posts are eligible.
- If needed, publish content that fits your configured age range.
📝 Note: If you already have eligible posts and Revive Social is still not posting, continue with the WP-Cron and Action Scheduler checks below.
Action Scheduler Support
Revive Social supports Action Scheduler, a more robust and scalable background processing library. If your site already uses a plugin that includes Action Scheduler (such as WooCommerce), Revive Social will automatically detect it and use it instead of the default WP-Cron system. This can improve the reliability and performance of scheduled posts.
If no such plugin is present, Revive Social will continue to function normally using WP-Cron, with no additional setup required.
Method 1.
You can create a Cron job for Revive Social using Cronjob.org:
Step 1.
Turn off the default WP Cron by editing the wp-config.php file (located in the root of the folder where WordPress is installed). Open the wp-config.php file, add a new line after define('WP_DEBUG', false); then add the following code on the new line:
define('DISABLE_WP_CRON', true);
Save your changes after you've added the new line.
If you are not sure how to navigate to this file via your Cpanel or FTP, you can install the following plugin, which will allow you to edit the files on your server directly from within WordPress: https://wordpress.org/plugins/file-manager-advanced/
Once the plugin is installed, you should have a new option called File Manager inside your dashboard. Click the menu item to bring up the files:
Right-click on wp-config.php and select E****ditor to start editing the file. Add the following line:
define('DISABLE_WP_CRON', true);Inside the file after define('WP_DEBUG', false); So it looks like below_:_
(Be sure to save your changes when you're done editing the file and then delete the File Manager plugin if no longer needed).
Once you have successfully turned off your default WP Cron, Revive Social will show a warning notice that your WordPress Cron has been disabled:
Step 2.
Create an account on https://console.cron-job.org/signup, then log into your account on the website.
Step 3.
Click the Create Cron Job button to create a new cron job.
Step 4.
Fill out the details of the Cron job. For Title, enter anything you wish; for Address, enter your website domain suffixed with /wp-cron.php?doing_wp_cron.
Example: https://yourwebsitedomain.com/wp-cron.php?doing_wp_cron
- Change yourwebsitedomain.com to your actual website domain.
- If your website does not have SSL, then change https to http
Step 5.
Set the Cron schedule; we recommend every 10 minutes:
Step 6.
Check the option to save responses so that you can see if the cron job is executed successfully, then click the Create Cronjob button.
That's it! Your cron job should now be created, and if you did Steps 4 & 5 correctly, then you should see success messages in the History section of https://cron-job.org, letting you know that the cron job ran successfully.
Method 2.
The other method to fix the issue is creating a true cron for your website. This requires you to have access to your cPanel account to make the following changes.
📝 Note: HostGator has gone ahead and created a pretty detailed document on how to create a true cron for WordPress, so we will use it. Please go here to view the document: How to create a true cron for WordPress. The screenshots from the article refer to HostGator, so the interface might be different according to the hosting provider.
If you are not comfortable with performing any of these methods, then we highly recommend you contact your web host for assistance. They will be able to perform either method for you in no time.
To dismiss the Revive Social notice regarding your WP Cron Job being disabled, simply click dismiss
Still, having issues? Contact us here: Submit Ticket