A Plugin Update Has Not Appeared Yet: What Small Businesses Should Do
Why might a WordPress plugin update not appear in my dashboard yet, and what should I do?
A release may not appear immediately because WordPress.org holds plugin and theme releases in a cooldown before distributing them through the update API used by dashboard notices and one-click updates. Do not assume that the delay means your site is broken or replace the recognised update route with an unverified download. Confirm the supplier’s release information, assess whether the update is genuinely urgent, and use your established support or maintenance process if waiting creates a material business risk.
A release may not appear immediately because WordPress.org holds plugin and theme releases in a cooldown before distributing them through the update API used by dashboard notices and one-click updates. Do not assume that the delay means your site is broken or replace the recognised update route with an unverified download. Confirm the supplier’s release information, assess whether the update is genuinely urgent, and use your established support or maintenance process if waiting creates a material business risk.
Why the dashboard may show an update later than the supplier
Plugin and theme releases go through a cooldown before WordPress.org distributes them through the update API. That update API powers the notices and one-click updates shown in normal WordPress dashboards. A supplier announcement and dashboard availability can therefore occur at different times without demonstrating that your website is broken.
Sources: Automated security review for plugin releases – Make WordPress Plugins; WordPress now checks plugin updates before release.
- Check the supplier’s announcement through its recognised website, account area or support channel.
- Confirm which plugin and version the announcement concerns.
- Keep the distinction between a release announcement and dashboard availability clear in your change record.
Do not replace the normal update route in a hurry
High-risk releases can be blocked from the update system as part of the automated security review. Waiting for the recognised update route is usually more proportionate than installing a file from an unfamiliar link, email thread or mirror simply because the dashboard update is late. If a supplier offers an alternative installation method through a verified official channel, evaluate it through your normal approval, testing and recovery process.
Sources: WordPress - WordPress is strengthening security for plugin… | Facebook; WordPress adds automated security checks to block risky plugin releases - Help Net Security.
- Do not treat an absent dashboard update as evidence that you need an unofficial installer.
- Do not let urgency remove source verification.
- Keep a recovery option available before manually installing any business-critical update.
Decide whether to wait, verify or escalate
Start by identifying the business function affected by the announced release and the consequence of waiting. A delay deserves faster attention when the release addresses a verified issue affecting payments, bookings, enquiries, customer access or another essential operation. If the need is verified and time-sensitive, contact the recognised supplier or your maintenance provider with the plugin name, current and announced versions, release notice and business impact.
- Wait when the release is routine and no verified business problem exists.
- Verify when the announcement is unclear or the affected version is uncertain.
- Escalate when a verified urgent issue affects an important business function.
- Do not present an unverified delay as an emergency.
Record the outcome for the next release
A brief record turns a confusing delay into a repeatable decision the next time it occurs. Record confirmed facts and decisions rather than assumptions about why a particular release was delayed.
- Release notice: date, supplier channel, plugin and stated version.
- Dashboard availability: when the update became visible, if known.
- Business impact: affected function and urgency.
- Decision owner: who chose to wait, verify or escalate.
- Outcome: update result, support response and follow-up action.
Update-availability response guide
Use this guide when a plugin supplier says a version has been released but it is not yet visible in your WordPress dashboard.
| Situation | Recommended response | What to record |
|---|---|---|
| Routine release with no current issue | Wait for normal dashboard availability and avoid unofficial download links. | Supplier notice, plugin version and date checked. |
| Announcement or affected version is unclear | Verify the release through a recognised supplier channel before taking action. | Channel checked and information confirmed. |
| Verified urgent business or security issue | Contact the recognised supplier or maintenance provider with the version and business impact. | Affected function, urgency, decision owner and support reference. |
This guide does not assume that every delay has the same cause. It preserves the recognised update route while providing a clear path for genuine business urgency.
Frequently asked questions
Does a missing dashboard update mean WordPress.org has blocked it?
Not necessarily. WordPress.org holds releases before update-API distribution, but a missing update alone does not establish the reason for an individual delay. Verify the supplier information and assess the actual business impact before escalating.
Should I download the update from a link sent by email?
Do not use an unfamiliar link merely because the dashboard update is unavailable. Prefer recognised supplier channels and apply your normal source-verification, recovery and approval process before using an alternative installation method.
When should I contact my maintenance provider?
Contact them when a verified release is needed to address a time-sensitive issue affecting an important business function, or when you need help confirming the appropriate update route, test plan and recovery option.
Related guidance
What follow-up questions matter most?
- Does a missing dashboard update mean WordPress.org has blocked it?
- Not necessarily. WordPress.org holds releases before update-API distribution, but a missing update alone does not establish the reason for an individual delay. Verify the supplier information and assess the actual business impact before escalating.
- Should I download the update from a link sent by email?
- Do not use an unfamiliar link merely because the dashboard update is unavailable. Prefer recognised supplier channels and apply your normal source-verification, recovery and approval process before using an alternative installation method.
- When should I contact my maintenance provider?
- Contact them when a verified release is needed to address a time-sensitive issue affecting an important business function, or when you need help confirming the appropriate update route, test plan and recovery option.
What steps does this workflow follow?
Respond safely to an unavailable plugin update
- Confirm the announcement: Check the supplier’s recognised channel for the plugin name, version and stated reason for the release.
- Assess business impact: Identify whether waiting affects a verified security, customer, revenue or operational problem.
- Choose a response: Wait for routine changes, verify unclear information, or escalate a verified urgent need through a recognised support channel.
- Record the outcome: Record the notice, dashboard availability, decision owner and final result for the next release.