--- title: "Package v21.13 - 01 October 2026" source: https://support.storeconnect.com/articles/package-v21-13 type: article format: markdown site: StoreConnect Support — product and developer documentation for StoreConnect site_index: https://storeconnect.com/llms.txt docs_index: https://support.storeconnect.com/llms.txt note: Append .md to any page or article URL on this site to get its Markdown form. --- # Package v21.13 - 01 October 2026 This release is mostly about giving Salesforce somewhere to record things it previously had no field for. An order gains fields for why it was cancelled, when, and by whom; an order line gains a field for the discount an operator applied by hand, separate from promotions and markdowns; and a customer record now shows when the customer confirmed their account. Sync also gets steadier: errors that usually fix themselves are held back from the error list while they heal and retried every five minutes, and a large record refresh is paced through a queue rather than launched all at once. Several display problems introduced by Salesforce Winter '27 are fixed. ## Breaking changes and cautions **A few Console actions may fail in the first minutes after upgrading** Some Console actions can fail briefly immediately after the upgrade and start working on their own without you doing anything. Nothing is lost, and no action is needed. If they are still failing hours later, raise a support case. [PKG-8867] **Login.gov appears as a provider option before the storefront supports it** **Login.gov** is now selectable in the **Provider** field on an **Authentication Provider** record, but the storefront release that signs customers in through it is not out yet. Selecting it now gives customers no working login option. Leave it unselected until the StoreConnect release notes confirm Login.gov support on your storefront version. The other four values added at the same time (**SAML**, **OpenID Connect**, **Keycloak OpenID**, and **SingleKey ID**) already work on current storefront versions. [PKG-9610] **Record refreshes are now paced, and a new Async Task object appears in your org** When your store asks Salesforce to refresh a set of records, the request is now queued as an **Async Task** record and worked through in priority order, instead of every object being refreshed at once. Objects that nothing else depends on go first, and a refresh no longer floods your sync pipeline while it runs. Because the queue works through one priority group at a time, a large refresh can take longer to finish than it did before. StoreConnect also sets a limit on how many sync rows a store can have in flight at once. The limit is managed for you and cannot be changed from your org. When it is in force, a large refresh paces itself against it rather than failing. **Async Task** is a queue StoreConnect manages, not a record type you work in. If you want to see where a refresh has got to, the records are readable: **Status**, **Retry Count**, and **Error Message** show the state of each task. Leave **Key** and **Payload** alone, since they record what your store asked for. Completed and failed tasks are deleted automatically seven days after they finish. [SYS-9666] ## Enhancements **Somewhere to record an order's cancellation** An order now carries **Cancelled At**, **Cancellation Reason**, and **Cancelled By User** (`Order.s_c__Cancelled_At__c`, `s_c__Cancellation_Reason__c`, `s_c__Cancelled_By_User_Id__c`), and an order line gains **Cancellation Reason** to sit alongside the **Cancelled At** and **Cancelled By User** it already had. A cancellation previously recorded who and when on each line, and nothing at all on the order itself. The three order fields appear in a new **Cancellation** section on the **Order** record page, below **Status**, and the line's reason joins the Order Product layout. They are available to the StoreConnect Administrator, Order Manager, and Sync permission sets. **Cancellation Reason** is a free-text field that nothing fills in automatically. Type the reason on the record when you cancel an order in Salesforce. A line cancelled on its own keeps its own reason rather than inheriting the one that closed the whole order, so a single returned item stays distinguishable from an abandoned order. [PKG-9832] **Somewhere to record an operator's own discount on an order line** Order lines gain **Unit Manual Discount** (`OrderItem.s_c__Unit_Manual_Discount__c`), for the per-unit discount an operator applied by hand. **Unit Discount** adds that figure together with the catalog markdown and any promotion, so there has been no way in Salesforce to tell an operator's own discount apart from the rest. The field appears in the **Discount** section of the Order Product layout, opposite **Unit Discount**. Like **Cancellation Reason**, nothing fills it in yet: the storefront release that records the figure on the line is not out, so the field stays empty until then. [PKG-10043] **Customer records show when the account was confirmed** Contacts gain **Account Confirmed At** (`Contact.s_c__Confirmed_At__c`), the date and time a customer confirmed their account, currently through the confirmation email link or by accepting an invitation. It sits with the existing **Invitation Accepted At** and **Password Reset At** timestamps. Blank does not always mean unconfirmed: customers activated another way, such as through a password reset or single sign-on, and customers confirmed before this release, have no value recorded. The field is read-only for Order Managers, since only the storefront writes it. [PKG-10410, EPS-3229] **More single sign-on providers are selectable** The **Provider** field on an **Authentication Provider** record gains five values: **SAML**, **OpenID Connect**, **Keycloak OpenID**, **SingleKey ID**, and **Login.gov**. The first four have been supported by the storefront for some time but were missing from the Salesforce picklist, so stores using them had no matching value to select. Login.gov is new and is not yet usable (see Breaking changes and cautions). The field also gains help text describing what it sets. [PKG-9610, WEB-9609] **Sync errors that fix themselves no longer clutter the list, and clear faster** Two kinds of sync failure are transient by nature: a record arriving before the record it points at, and a change event Salesforce could not interpret on first pass. Both usually clear on their own within minutes, but until now they appeared in the sync error list, the error type filters, and the error counts and summary totals, so an administrator could not tell a real problem from one already resolving itself. These two error types are now held back from those places for their first 20 minutes, which is the window in which they usually heal, and the automatic retry picks them up every five minutes during it. One that is still failing after 20 minutes appears in the list like any other error, so nothing is hidden from you permanently. Every failed event, transient or not, is still swept once an hour within the same 12-hour window as before. Retrying a record by hand also sweeps up any held-back transient failures created within an hour either side of it, up to 200 records in one click, so a manual retry clears the whole cluster rather than just the row you selected. The automatic retry now also stops properly if sync is disconnected partway through a run, instead of continuing to recycle failed events for the rest of the hour. [SYS-9639] **Resending a record no longer loses its values** When your store resent a record Salesforce already held, the record was rejected as a duplicate and its field values were dropped. Salesforce now recognizes the existing record and applies the incoming values as an update instead, so retries and resends are safe to repeat. Duplicate rule settings are still honored exactly as before. [SYS-9639] **Large refreshes send far less data** Records in a bulk refresh are now packed together into a single change event rather than sent one per record, which cuts the number of change events a large refresh produces by a wide margin. Combined with the pacing described above, this is what keeps a full refresh from backing up your sync queue and holding up the everyday changes waiting behind it. [SYS-9661] ## Deprecated fields No fields are removed or deprecated in this release. :::note Two existing behaviors change meaning rather than being deprecated. The `sc_sync_auto_retry_interval_minutes` key in **Setup Configuration** now sets an hourly schedule by default rather than a two-hourly one, and the five-minute transient retry runs inside that schedule regardless of the value you set. Refresh requests are now queued rather than started immediately, so a large refresh can finish later than it used to even though it moves the same records. ::: ## Fixed bugs **Confirmation emails were missed at signup in Person Account orgs** In orgs that convert customers to Person Accounts, a storefront signup arrives as three records written together: the account, the contact, and the confirmation. The customer was converted to a Person Account before the confirmation was applied, and Salesforce refuses to update a contact in the same operation as that customer's conversion, so the confirmation failed and no confirmation email went out. The email only arrived later, when the automatic retry re-ran the failed step. Conversion now runs after every update in the batch has been applied, so the confirmation lands first and the email goes out at signup. Orgs that do not use Person Accounts, or that have left **Person Account Conversion Record Type** blank, are unaffected. This affected orgs on v21.5.0 and later. [PKG-10184] **Salesforce Winter '27 broke several StoreConnect screens** Salesforce Winter '27 changed how icon buttons are sized, which pushed several StoreConnect screens out of shape. The expand arrow in the content tree inflated every row it sat in; the undo and edit icons in the sync error panel outgrew their rows; and the Salesforce Id button in the sync errors table painted over the column next to it. StoreConnect now draws these icons itself, so a future Salesforce change cannot resize them again. The Salesforce Id column becomes a link: it shortens with an ellipsis like its neighbors, shows the full Id when you hover, and can be middle-clicked to open in a new tab. Also fixed in the same work: the store filter on the Agent Access screen grew a horizontal scrollbar on long store names instead of shortening them; menu hover color differed between the Console and the Synchronization and Stock Management tabs depending on which you had opened first; the "open field definition" icon in the picklist manager threw a script error when clicked; the setup wizard failed to load instead of showing its no-permission message when a user's profile name was hidden, which Winter '27 makes more likely; and rows in the sync error panel that held staged or multi-value data showed an undo control that could not be clicked. [PKG-9759] **Draft content changes that set a checkbox to on applied as off** A draft content change that turned a checkbox on was applied as off when the change was published. The storefront stores a staged checkbox value in a form Salesforce did not recognize as "on", so every one of them was read as off. Salesforce now recognizes the full set of values, which also repairs drafts staged before the fix. If you have unpublished drafts that set a checkbox, check the result after publishing them. **A customer could be converted to a Person Account by a resent record** With the resend handling described under Enhancements, a resent contact record could reach the Person Account conversion carrying a real Salesforce Id and its account link, which could convert an existing business account into a Person Account. Resent contacts are now excluded from conversion, so only genuinely new customers convert. [PKG-10184] --- ## Follow StoreConnect - [Email Newsletter](https://storeconnect.com/c/lp-newsletter) - [LinkedIn Newsletter](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7444956928444862464) - [YouTube](https://www.youtube.com/channel/UCngKdP2x8l1wcbAKW3tvU8g) - [LinkedIn](https://www.linkedin.com/company/storeconnect) - [X / Twitter](https://x.com/storeconnecthq) ## Popular Links - [Partners](https://storeconnect.com/partners) - [Become a Partner](https://storeconnect.com/become-a-partner) - [News](https://storeconnect.com/articles/news) - [Events](https://storeconnect.com/articles/events) - [Live Events](https://storeconnect.com/live-events) - [Feature Comparison](https://storeconnect.com/how-we-compare) - [Download a free trial](https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000FMkeKUAT) - [Book a Demo](https://storeconnect.com/contact) ## Documentation - [Help documentation](https://support.storeconnect.com/help-documentation) - [AI agents](https://support.storeconnect.com/ai) - [Videos & tutorials](https://support.storeconnect.com/videos-tutorials) - [Developer reference](https://support.storeconnect.com/developer-reference) - [Release notes](https://support.storeconnect.com/release-notes) - [Troubleshooting](https://support.storeconnect.com/troubleshooting) - [Trust Center](https://trust.getstoreconnect.com/) - [Status Page](https://status.storeconnect.com/) ## Contact - info@getstoreconnect.com - US +1 415 745 3230 - AUS +61 2 8365 2308 100 S Ashley Dr, Suite 600-2461 Tampa FL 33602-600 USA Level 22, Sydney Place 180 George Street Sydney, NSW, 2000, AUS ## Machine-readable - [Site index for agents](https://storeconnect.com/llms.txt): curated map of the StoreConnect site in llms.txt format - [Documentation index for agents](https://support.storeconnect.com/llms.txt): full technical and product documentation map Every page and article on this site has a Markdown rendering: append `.md` to its URL. Continue in Markdown: [Help documentation](https://support.storeconnect.com/help-documentation.md) · [Developer reference](https://support.storeconnect.com/developer-reference.md) · [Videos & tutorials](https://support.storeconnect.com/videos-tutorials.md) · [Release notes](https://support.storeconnect.com/release-notes.md) --- StoreConnect Support — https://support.storeconnect.com/articles/package-v21-13