Push a patch version from your Partner Business Org to every subscriber org running a compatible prior version, on a schedule you control.
- Build a patch version
From the package detail page in your Partner Business Org, click New Patch. Select the base version you are patching. Salesforce creates a patch development org seeded with the prior package contents.
- Make and test changes
Open the patch development org. Add or change only the metadata the patch namespace permits: no Apex API breaks, no field deletions, no signature changes. Deploy to a scratch org or a friendly subscriber and verify.
- Upload the patch
Back in the Partner Business Org, click Upload on the patch version. Salesforce runs the same security and packaging checks as a normal upload. You receive a new install URL when it succeeds.
- Open the Subscriber Support Console
From the package detail page, click Push Upgrades. The console shows every subscriber currently on a version eligible for this patch.
- Select targets and time
Filter the subscriber list. Pick the org IDs you want to push to. Choose a UTC scheduled time at least 48 hours in the future. Add a description that will appear in the post-push email to the subscriber admin.
- Submit and monitor
Submit the push. Salesforce queues the job. Refresh the console to watch the success and failure counts. Investigate any failures and either patch the conflict or retry that subset later.
The new patch version every selected subscriber org will receive at the scheduled time.
Org type, region, last package activity, and explicit org-ID list. Used to scope the push to a safe initial cohort.
UTC timestamp for when Salesforce begins deploying. Falls inside the subscriber instance maintenance window.
Free-text description that appears in the email sent to the subscriber admin after the push completes.
Controls whether Salesforce reattempts a failed push at the next maintenance window automatically.
- Push Upgrades only work between patch versions of the same minor release. They cannot bump a major version, and they cannot move a subscriber between two different packages.
- If a subscriber org has paused upgrades from Setup, Installed Packages, your push skips that org. The console marks it as Excluded, not Failed, so watch both counts.
- A push deploys metadata, not data. Custom Setting values, Custom Metadata records, and any subscriber-created data stay untouched, even when the patch redefines the underlying types.
- Schedule pushes outside the subscriber business hours. The deploy itself is online, but any Apex retries or flow re-evaluations that follow can surprise end users mid-task.