1. LandOffer
  2. Blog
  3. All articles
  4. Salesforce Certification Maintenance: Find the Required Trailhead Modules Before the Deadline

Career Growth

Salesforce Certification Maintenance: Find the Required Trailhead Modules Before the Deadline

A completed fictional two-credential ledger separates Developer Winter ’26 maintenance from Administrator Spring ’26 requirements. A 30-hour status-discrepancy record and unsent support draft preserve linked-account checks, all-unit completion evidence, current PT deadlines, and the distinction between a badge and confirmed certification maintenance.

9 min readLandOffer team

Find Salesforce maintenance by matching your exact certification, earned date, required release badge, and deadline. Complete every required unit using the Trailhead account linked to the credential, then verify the certification's maintenance status. A different badge, an older release, or a public module listing does not establish completion of your assigned maintenance.

This LandOffer.ai guide builds a two-credential task ledger and a completed status-investigation packet. Public Salesforce sources were checked on October 27, 2026. The holder, dates of personal completion, account observations, and support draft are fictional. No account was accessed, challenge completed, profile changed, verification email requested, or support case sent.

A board maps Developer Winter 26 to December 4, 2026 PT, and Administrator Spring 26 to April 16, 2027 PT; an Old Badges folder remains separate.

Match the full credential name and release first

Salesforce's maintenance schedule maps credentials to required maintenance badges. It also notes exceptions and grouped requirements, so do not turn a general statement about annual maintenance into a rule that every credential needs the same activity. The schedule says its dates use Pacific Time and are subject to change.

The release label is part of the requirement. “Winter '26” is not a generic invitation to take any winter-themed training, and a Spring badge does not automatically satisfy a Winter requirement. Keep the full title and official link beside the credential instead of relying on search results or a short bookmark name.

Eligibility dates matter too. The Winter '26 notice lists December 4, 2026, for the relevant maintenance deadline and specifies an earned-on-or-before date for each listed credential. For Platform Developer, the stated cutoff is December 8, 2025. A holder's own requirement must still be checked against the linked credential record.

For comparison, the Platform Administrator Spring '26 notice applies to holders who earned that credential on or before April 22, 2026, and gives April 16, 2027, as the deadline. Completing the Developer task does not close the Administrator task; each has its own release and due date. The dates are current public examples, not a universal deadline for all readers.

Use the schedule to identify the likely requirement and the credential-specific notice to check its conditions. Then compare them with your personal maintenance information. If they disagree, preserve the exact titles, links, and dates and ask Salesforce to resolve the discrepancy; do not choose whichever deadline gives you more time.

Build a complete maintenance task ledger

Fictional holder Taylor has two credentials: Platform Developer earned May 10, 2025, and Platform Administrator earned June 20, 2025. Both earned dates precede the public cutoffs above. Taylor begins the review on October 27, 2026, without assuming that completing one maintenance badge will update both credentials.

Here is Taylor's completed task-identification record. The account and badge states are invented for the case, while the linked requirement names and public deadlines come from Salesforce's current pages.

Credential and earned date Required task identified Public deadline and personal check Recorded next action
Platform Developer; May 10, 2025 Platform Developer Certification Maintenance (Winter '26). December 4, 2026, PT. The fictional personal record shows the same requirement as due. Open the exact linked module and complete both required units, with an internal target of November 18.
Platform Administrator; June 20, 2025 Platform Administrator Certification Maintenance (Spring '26). April 16, 2027, PT. The fictional personal record shows this separate requirement as due. Plan this badge separately; internal target February 10, 2027. It is not covered by Developer maintenance.
An older Administrator maintenance badge Previously completed Spring '25 learning in Taylor's fictional history. It is not the Spring '26 badge named in the current requirement. Keep it as history; do not mark the new requirement complete from the older badge.
An unrelated Flow learning badge General learning completed during the fictional preparation period. No mapping to either required maintenance task has been established. Useful learning only; exclude it from the maintenance-complete decision.

Taylor records the exact linked account and private profile reference in the real version of this ledger, not a password or authentication token. In this educational example, no real profile identifier is created or displayed. There is no need to make an account public merely to organize personal maintenance work.

The internal targets provide room for checking results. They do not replace Salesforce's deadlines, establish an extension, or promise enough time to solve every technical problem. The ledger also avoids inventing a precise last-minute cutoff: the public schedule supplies PT dates, and a holder should confirm any exact cutoff before relying on it.

For the Developer task, the actual public module lists two units: the release-maintenance learning unit and “Get Hands-On by Running Apex and Flow Tests Together.” Taylor must account for both. Reading the first page or seeing its estimated duration does not establish completion of the second.

The Administrator Spring '26 module currently lists one learning unit. Follow the actual module's current requirements rather than copying the unit count, format, or time estimate from another badge. Public “Incomplete” labels shown outside a signed-in learner account do not reveal Taylor's personal completion state.

Complete the assigned learning without confusing the evidence

Before doing the maintenance work, confirm that the signed-in Trailhead identity is the one linked to the certification. A familiar browser session can be the wrong account. Check the identity through the normal account interface; do not copy credentials into a support draft or change someone else's profile to force a match.

Work through every required unit and assessment. If the module calls for a practice environment, follow that module's instructions in an appropriate learning environment. This guide does not launch a Playground, install a package, run Apex, or provide answers to a maintenance assessment. A real challenge result must come from the holder's own completed work.

Taylor's fictional record says the Developer module was completed on November 18, 2026, at 09:00 PT, with both units marked complete on the linked account. That statement is invented to demonstrate the next verification step. It is not an observed Salesforce result or a claim that the publisher earned the badge.

Taylor retains the full badge title, completion date, unit-completion evidence, and account association. A trail progress percentage does not identify the exact maintenance requirement or establish that every required unit is complete. Nor would a screenshot of a successful technical action, without the badge's own completion record, establish that the whole module is finished.

Badge Completion shows Unit 1 and Unit 2 checked while Certification Status says Still Due; a clock and Support Draft marked Unsent sit between the records.

Investigate a completed badge whose status has not updated

Salesforce's status-verification article distinguishes personal maintenance status from the public certification information other people may see. It recommends checking the linked account and allows time for synchronization. Its troubleshooting steps use up to 24 hours, while other notes on the same page refer to up to one business day. Do not translate either into an instant-update promise or a reason to wait until the deadline.

Taylor checks again on November 19 at 15:00 PT, 30 hours after the fictional badge completion. The module still shows complete, but the Developer credential still shows maintenance due. Taylor does not rename that state “active and current” in a personal tracker.

The completed investigation record is:

Check Fictional observation and disposition
Exact release The completed title is Developer Winter '26, matching the due requirement. The older Administrator badge is irrelevant to this discrepancy.
All required units Both Developer units appear complete in the fictional account; the investigation is not based only on the reading unit.
Account association Taylor checks the linked identity and confirms the same account within the case. No account merge or email change is attempted.
Time elapsed November 18 at 09:00 to November 19 at 15:00 is 30 hours. Completion and recheck timestamps are recorded with PT.
Certification status The Developer maintenance state is still due at the recheck. The Administrator task remains separately outstanding.
Evidence prepared Badge-completion view, relevant credential-status view, full titles, timestamps, and the account email for a private support request. No passwords, tokens, or unrelated learner records.
Disposition Prepare a support case and retain its eventual reference and response if sent. No case has actually been submitted and no resolution is assumed.

The unsent support draft reads:

My Platform Developer credential still shows maintenance due after completion of Platform Developer Certification Maintenance (Winter '26). My records show both required units completed on November 18, 2026, at 09:00 PT; I rechecked on November 19 at 15:00 PT. The completed badge and credential are associated with the same linked account in my records. I have the relevant completion and status screenshots for a private case. Please confirm whether the required maintenance has been associated with this credential and advise what further evidence is needed. I am not requesting that an incomplete requirement be marked complete.

This draft is based on a hypothetical due-status discrepancy. Salesforce's published steps specifically discuss cases still showing expired, so do not invent a guaranteed remedy for a different status. Provide the actual state and follow the appropriate support route. If a real credential is expired, its applicable expiration and recovery rules need separate confirmation.

Keep deadline monitoring tied to the unresolved task

As of October 27, the fictional review date, December 4 is 38 calendar days away. Taylor's November 18 internal target leaves 16 days to the public deadline date. The retained calendar checks establish those day intervals only, not support availability or an exact account cutoff.

Taylor keeps the Developer item open until the certification's maintenance record is reconciled. Keep learning completion and support preparation as intermediate states until the actual certification record is reconciled. A support case reference, if one later exists, also does not itself prove that the underlying requirement was applied.

For the Administrator item, Taylor retains the distinct Spring '26 title and April deadline. A reminder should name that exact task rather than say “all Salesforce maintenance.” If another credential is added, inspect its own mapping and any combined requirements; do not multiply or remove tasks based only on a badge name shared with another credential.

When a personal requirement or deadline changes, preserve the newer account information and the dated source that prompted the original plan. That makes a follow-up understandable. It also avoids treating an old reminder or a screenshot from months ago as the final authority on what is due today.

Close the record only when the credential agrees

Taylor's local closeout reads: “Developer Winter '26 learning complete within the fictional case; certification maintenance status unresolved; support draft prepared and unsent. Administrator Spring '26 task remains outstanding.” There is no fabricated status update or claim that both credentials were maintained.

For your own maintenance, start from the exact credential-to-badge match, complete the whole required module under the linked identity, and then check the credential record. Keep the full badge title, PT deadline, completion evidence, and unchanged credential state together until the discrepancy is resolved. LandOffer.ai publishes this credential-maintenance guide; Salesforce determines the requirements and the status of each certification.

Sources and Further Reading