Skip to content
Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Winter '27 overview
For Developers

Winter '27 for Developers

API 68.0, a bigger Apex heap, Apex integration tests in preview, AIforce tooling and the authentication deadlines.

A Queueable job that died with "Apex heap size too large" last quarter now finishes in your preview sandbox without a single code change. Winter '27 raised the asynchronous heap from 12 MB to 25 MB, and that is the easy part of the release. The harder part is authentication: a SOAP login() permission that enforces on December 1, OAuth flows that retire on February 20, 2027, and an AI tooling layer Salesforce now calls AIforce.

This is the developer's map of Winter '27. API version 68.0 ships with it. Release notes first published the week of August 17, 2026, sandbox preview began the weekend of August 28-29, and production orgs upgraded through the weekend of October 9-10, 2026. AIforce and several Agentforce features release monthly, so some items below arrived in October and November.

API 68.0 and what retires behind it

Winter '27 is API version 68.0, and LWC API 68.0 "has no version-specific changes." So bump your components first, one version at a time. Apex, the Flow runtime and the Streaming API do have 68.0-specific behaviour, so test those separately.

The REST API now accepts latest in place of a version number in the URI, which routes to the newest version your org supports. Use it in scripts and tooling, not in production integrations where you want the version pinned.

Two retirements are scheduled behind 68.0:

  • Platform API versions 31.0 through 40.0 are deprecated in Summer '27 and retired in Summer '28. After retirement, calls to those versions fail. Move to 41.0 or later.
  • Apex saved at API 9.0 through 19.0 now produces a compiler warning that the version "is scheduled for retirement," with no date given yet. The warning shows in Setup, Salesforce CLI, the VS Code extensions, Web Console and the Tooling API.

Apex: more heap, real callouts in tests, and new Tooling resources

Heap limits went up. Synchronous heap rose from 6 MB to 10 MB and asynchronous heap from 12 MB to 25 MB. It applies automatically as each instance upgrades, and Limits.getLimitHeapSize() confirms the value. Sandboxes, Developer Edition and scratch orgs get an Apex Settings option, "Enforce the Summer '26 Apex heap limit," so you can test code that still has to deploy to a production org on the old limit. In Spring '27 the higher limits apply everywhere regardless of that setting. Our heap limit deep dive covers what actually sits on the heap and which workarounds you can now delete.

Apex integration tests (Developer Preview). You can write tests that call real HTTP endpoints and External Services through named credentials, without mocks. Enable the ApexIntegrationTests feature in a scratch org definition file, annotate the class and each test method with @IntegrationTest, set up shared data in a @BeforeClass method, and clean up committed data in a @TearDown method. Runs go through the Tooling API runTestsAsynchronous resource, only one integration run can be active at a time, and a mock registered with Test.setMock() still wins over the real callout. It is scratch-org only, and the release note is blunt: do not build production functionality on it. Our integration tests guide walks through the lifecycle.

Elastic limits now cover Batch Apex (Beta). When asynchronous jobs exceed the rolling 24-hour limit, in-flight batch processing is throttled and new batch jobs are limited to one active job at a time. Turn on "Use elastic limits for asynchronous Apex jobs (beta)" in Apex Settings and watch usage with the OrgLimits methods. Nonproduction orgs get an override field so you can rehearse the throttling with a small limit.

Apex Symbol API (Beta). A new Tooling API resource, GET /services/data/vXX.0/tooling/symbols, returns type information for built-in, custom and dynamic Apex types. The category parameter takes builtin, database or dynamic, and you can filter by namespace and name. Salesforce names three uses: IDE code completion, context for AI agents that generate Apex, and grounding for setup agents. Our Apex Symbol API article covers what it returns and what it still does not.

Recompile only what is broken. New Setup buttons, "Compile only invalid classes" and "Compile only invalid triggers," plus a Tooling API resource, POST /services/data/vXX.X/tooling/apexCompileResults, recompile invalid classes and triggers instead of the whole org.

A few smaller changes are worth a line each:

  • Explicit namespaces in packaged SOQL. Database.QueryOptionsBuilder with .withExplicitNamespace(true) resolves a packaged field correctly when a subscriber creates a field with the same name.
  • Cursors for Data 360 objects (Beta). Database.getCursor() and Cursor.fetch() now work on data model objects, with new Limits methods for cursor rows. Cursors expire after 24 hours.
  • Elliptic curve crypto. The Crypto class adds EC key pairs, JWE encryption through ECDH-ES and EC signing, and a new JweToken class parses tokens.
  • Custom row causes on standard objects. Apex shares on objects such as Account and Case previously had to use the Manual row cause, which Salesforce deletes when the record owner changes. Custom row causes avoid that, and Salesforce's developer blog said they were due to reach all orgs by the end of October.
  • Two release updates to schedule. Blocking anonymous Apex execution from managed package sessions enforces in Summer '27. Rolling back platform event trigger transactions on unhandled exceptions enforces in Spring '27, so partially written records stop being committed.

Lightning Web Components

The LWC changes are modest, which suits a version bump.

  • Third-party web components are generally available. Render them with the lwc:external directive. Nothing changed since the beta.
  • State managers get refresh(). Call it on a built-in state manager once its status is loaded, and it resolves after data holds fresh values. Useful for related list records.
  • AI metadata tags now fail deployment. Adding an <ai> element to an LWC config file or <design:ai> to an Aura design file is rejected. Existing components keep working.
  • The Lightning Web Security window.open() change was rolled back. Same-origin window.open() calls were going to throw. Salesforce disabled that change, and no action is needed.
  • Salesforce Microfrontend (UI Embedding) is generally available. Embed an existing web app in a Salesforce page and exchange data, styling and events with the page over a secure channel.

One Aura release update is queued: removing non-public fields from custom object data in Aura action responses enforces in Spring '27.

APIs, events and data access

  • SOQL FORMULA() in WHERE clauses (Beta) allows arithmetic and field-to-field comparison in a filter.
  • Streaming API replay watermark. On API 68.0, every successful /meta/connect response carries a per-channel replay watermark, so clients can advance their replay ID without waiting for an event.
  • OpenAPI for the sObjects REST API (Beta) gets a newer spec that covers all resources and wildcards.
  • Bulk API 2.0 adds a refresh operation for marketing objects that replaces all data in the target set.
  • GraphQL API guest access. Admins can now control unauthenticated guest access to the GraphQL API.
  • Standard-volume platform events retire on December 15, 2026. Salesforce provides a one-click migration to high-volume platform events. Do it in a sandbox first and rerun your subscriber tests.

The authentication calendar

This is the section to put in front of your integration owners.

  1. November 30, 2026: the OAuth 2.0 device flow works only with local External Client Apps. Connected apps using it must migrate.
  2. December 1, 2026: every user who calls SOAP login() needs the Use Any API Auth permission, enforced uniformly across production and sandboxes. Without it, login() returns an error.
  3. February 20, 2027: the OAuth username-password flow for connected apps retires (moved from Winter '27), along with the user-agent and hybrid user-agent flows. Orgs created in Summer '26 or later already have the username-password option disabled. Replace it with the web server flow with PKCE for user logins or the client credentials flow for server-to-server.
  4. Instanced URLs: API traffic must use your My Domain login URL. Enforcement is phased, starting in sandboxes in October 2026 and production in January 2027. SOAP logins against a custom domain fail with HTTP 400 when blocking is on.
  5. Summer '27: the SOAP login() call in API versions 31.0 through 64.0 retires, and connected apps stop receiving bug fixes and support.

Two quieter changes affect long-running integrations now. Idle refresh tokens expire after 30 days, enforced in sandboxes from October 21 and production from November 4, 2026. An integration that runs once a quarter will fail with INVALID_SESSION_ID or an OAuth error, so give it a fresh token schedule. And the OAuth 2.0 DPoP extension is available to bind tokens to the client's private key, with a matching Apex method in the Auth namespace. ISVs get a migration tool that turns packaged connected apps into packaged External Client Apps while keeping existing tokens valid.

AIforce: Agentforce Vibes, Multi-Framework and MCP servers

As of September 4, 2026, Salesforce rebranded Headless 360 as AIforce, a new top-level section of the release notes that covers Agentforce Vibes, Salesforce Multi-Framework and Salesforce MCP Servers. Features there ship as often as monthly.

AI Skills. Salesforce publishes curated skills for LWC, Flow and Apex in the forcedotcom/sf-skills repository. Install them for Claude Code, Codex or another compatible CLI with npx skills add forcedotcom/sf-skills. In Agentforce Vibes they install and update automatically. The repository also carries skills for sandboxes, scratch orgs, Dev Hub and packaging, such as platform-sandbox-configure and dx-packaging-push-upgrade-configure.

The Salesforce Development plugin for Claude Code. Installed from Anthropic's plugin marketplace, it combines skills, Salesforce CLI, hosted MCP servers, agents, hooks and commands, and it can now discover specialized plugins when a project needs more than the core one. You approve each install.

Multi-Framework apps as microfrontends. Help removed the beta disclaimer the week of November 9, though Salesforce's October developer blog still calls it a beta. You can embed a deployed Multi-Framework app (React or Angular, on the salesforce.app domain) in Lightning pages or Experience Cloud pages through a thin LWC that renders lightning-ui-embedding. Orgs must be on Hyperforce. A Multi-Framework Insights dashboard in Scale Center (Beta) shows page views for your top ten apps.

Hosted MCP servers. The Metadata Grounding MCP Server (Beta) gives AI clients read-only, permission-aware access to org metadata across more than 60 types, queried through Salesforce Catalog. The CMS Content Read-Only server is generally available with 21 tools, and a new Content Write server adds 15, though for now both work only in Developer Edition, scratch orgs and sandboxes, with Agentforce Vibes as the only supported client. You can create custom Salesforce-hosted MCP servers headlessly through the API Catalog Connect REST API, and users can reach external MCP servers with their own OAuth credentials instead of a shared integration user. Both of those last two are generally available.

Tooling, DevOps and packaging

Web Console is the in-org IDE. Developer Console is hidden by default in Winter '27 and in maintenance mode, with only high-severity security fixes. Web Console, a browser IDE built on VS Code for Web, replaces it and needs the Web Console User and View All Data permissions. If you still need the old tool, an admin can switch "Enable Developer Console" back on under Setup, Web Console.

Next Generation DevOps Center is now Lifecycle Center. The rename rolled out from September 28, 2026, and the DevOps Center managed package keeps its name. Lifecycle Center Governance (Beta) defines policies that apply to coding agents in Agentforce Vibes, mapped to checks such as Code Analyzer rules. A generally available migration moves DevOps Center managed package projects, pipelines and work items into Lifecycle Center from the first week of November. Validate-only deployments and Jira work item import arrived too. In sandboxes and scratch orgs, DX Inspector can validate metadata against a target without deploying and redeploy a previous deployment after edits.

Packaging and Security Review. ISVs can push-migrate up to 100 subscriber orgs a day from first-generation to second-generation packages, up from 5. Security Review now scans UI bundles for client-side risks, so packages with React bundles need a Code Analyzer v5 report from the uibundle engine. Salesforce Functions is no longer available for purchase or renewal.

ISVs have three more dated items. Trialforce now requires a verified email-sending domain in the Trialforce management org to create new source orgs, and existing templates need one before February 22, 2027, or their custom branded addresses are replaced with a substitute. Partner Console registers packages to the License Management Org through OAuth with MFA instead of stored LMO credentials. And new AI skills cover post-install configuration, push upgrades and the full move from first-generation to second-generation packaging, from the same sf-skills repository.

Agentforce for developers

Agents got easier to move between orgs. From API 68.0, the new AiAgentDefinition and AiAgentDefinitionVersion metadata types let Salesforce CLI retrieve an agent and its dependencies, where it previously took at least three types. Agents written in Agent Script also need AiAuthoringBundle. Managed packaging of agents is not supported.

Multi-Agent Orchestration is generally available, so an orchestrator agent can call other agents in the same org as subagents. Agent Memory is generally available too: set memory: enabled: True in the Script view context block, and admins have an org-wide switch to turn conversational memory off. Agents now accept file uploads, but from the week of October 12 they default to an error unless your script declares the file-upload parameter and a mode. Test that before a customer sends a screenshot.

Flow testing from the developer's chair

Flow Test Mode and mock outputs for Action and Subflow elements give admins assertion-based tests for autolaunched and record-triggered flows, and Help now lists both as generally available. Developers can generate draft test scenarios from a terminal with headless Agentforce for Flow, and the Tooling API's FlowTestResult gained Error and FailedAssertions fields for CI reporting. One source control note: auto-layout flows now write every End element explicitly to the flow XML on save, so expect one noisy diff the first time each flow is saved.

What this release means for developers

Winter '27 gives developers more room and less legacy. The heap increase, invalid-only recompile and the Symbol API make daily work smoother. The authentication changes are the real project: Use Any API Auth on December 1, the OAuth flow retirements on February 20, 2027, and SOAP login() and connected app support ending in Summer '27. AIforce is where Salesforce is investing, and skills, hosted MCP servers and Multi-Framework microfrontends are worth a sandbox afternoon now.

Run the checklist below in a preview sandbox or a scratch org. For the admin view of the same release, see Winter '27 for Admins. For the identity and integration architecture behind these dates, see the Architect article. The Top 10 covers the changes that matter regardless of role.

Sources

What to test in your sandbox

  1. 1. Bump components and classes to API 68.0

    Raise the API version on a branch, one version at a time, starting with LWC bundles because LWC 68.0 has no version-specific changes. Run your Jest and Apex tests in a sandbox or scratch org, and remove any AI metadata tags from component configuration files before deploying, since they now fail deployment.

    Reference: api-version, lwc, scratch-org

  2. 2. Retire heap workarounds behind tests

    Run your largest synchronous, Queueable and batch jobs in a Winter '27 org and log Limits.getLimitHeapSize() to confirm the 10 MB and 25 MB limits. Remove one chunking or serialization workaround at a time, with a test that loads realistic data volumes, so a later regression shows up in CI rather than in a production job.

    Reference: apex, governor-limits, batch-apex

  3. 3. Inventory SOAP login() callers and OAuth flows

    Query Login History for SOAP logins and for username-password, user-agent and device flow OAuth grants over the last 90 days. For each integration, grant Use Any API Auth before December 1, 2026, then move it to an External Client App with the web server flow with PKCE or the client credentials flow before February 20, 2027.

    Reference: soap-api, oauth, external-client-app-manager

  4. 4. Replace instanced hostnames with My Domain URLs

    Search code, named credentials, middleware configuration and CI scripts for instance hostnames and legacy domains in API calls. Replace them with your My Domain login URL. Enforcement started in sandboxes in October 2026 and reaches production in January 2027, and SOAP logins against a custom domain fail once blocking is turned on.

    Reference: my-domain, named-credential, api

  5. 5. Try Apex integration tests in a scratch org

    Enable the ApexIntegrationTests feature in a scratch org definition file, then write a test class with @IntegrationTest, a @BeforeClass setup method and a @TearDown cleanup method that calls a real endpoint through a named credential. Run it through the Tooling API runTestsAsynchronous resource, and keep it out of production pipelines while it is a Developer Preview.

    Reference: apex, test-class, named-credential

  6. 6. Migrate standard-volume platform events

    List every standard-volume platform event in the org and run the one-click migration to high-volume events in a sandbox before December 15, 2026. Rerun subscriber tests for Apex triggers, flows and external subscribers. Then review error handling for the Spring '27 update that rolls back the whole platform event trigger transaction on unhandled exceptions.

    Reference: platform-event, apex-triggers

  7. 7. Set up AI Skills and Web Console

    Install the curated skills with npx skills add forcedotcom/sf-skills in your coding client, or use them automatically in Agentforce Vibes. Open Web Console in a sandbox and confirm developers hold the Web Console User permission, since Developer Console is now hidden by default. Re-enable Developer Console only if a workflow still depends on it.

    Reference: agentforce-vibes-extension, developer-console, scratch-org

Related dictionary terms

Read overall highlights →See top 10 features →See Admins take →See Architects take →See Consultants take →

Practise it

Five questions on Platform Developer I

Exam-style questions with an explanation after each one. No account needed, and your answers build a weak-topic map once you have one.