Salesforce Known Issues

Sandbox and NA44 errors when accessing BLOB/CLOB fields or installing AppExchange packages

Content and Files , Packaging , VisualForce , Sandbox , Winter 19

Salesforce transactions that are creating or modifying binary data type fields, also known as BLOBs, and subsequently perform rollback operations either implicitly (Apex test method completion) or explicitly (manual savepoint capture and rollback) may encounter errors attempting to access those fields...

In Review ·Reported By 38 ·Updated 2 days ago

Pending Deployments - CS88

Metadata , Sandbox

Deployments through Developer or Developer Pro Sandboxes on CS88 is either slow or taking a long time.

In Review ·Reported By 89 ·Updated 4 days ago

Data Loader OAuth login may fail when using saved usernames and Server host setting is changed unexpectedly

Data Loader , Sandbox

When attempting to login using Data Loader's OAuth option, users encounter a generic error: Please check your username and password. If you still can't log in, contact your Salesforce administrator. And no login attempt may be present or recorded in the user record's login history. In addition,...

In Review ·Reported By 19 ·Updated 3 days ago

Multiple Emails getting triggered after Sandbox Refresh (Post Refresh Script)


Multiple emails getting triggered after sandbox refresh which is performing an action via post install refresh apex class.

In Review ·Reported By 1 ·Updated 3 days ago

Scratch orgs hit Internal Server Error when trying to add a role to a user record in the newly created org.


When the customer creates a scratch org they hit an Internal Server Error when trying to add a role to a user record in the new org. The errors can be -2074079576 or -117023207 (or others) R&D have advised that if they wishes to use Salesforce's "out-of-the-box" Roles, they should use a scratch org...

In Review ·Reported By 37 ·Updated 4 days ago

Scratch org creation fails with Error ID (1203833999) without providing any details on troublesome components/features.

Sandbox , Salesforce DX

Scratch org creation fails with below error without providing details on troublesome components/features. === Component Failures [1] TYPE FILE NAME PROBLEM ───── ───────────────────────────────────── ───────────── ────────────────────────────────────────────────────────────────────────────────────────────────────────────── Error...

In Review ·Reported By 12 ·Updated 4 days ago

If a sandbox clone is deleted and the source organization no longer exists the sandbox clone will be left in an active state.

Sandbox , Spring 19

If the source sandbox for a clone no longer exists(it was either deleted or has since been refreshed) a clone of that sandbox will remain active if the user deletes the sandbox from production. The listing will no longer be visible but, the sandbox will still be accessible and if a new sandbox is created...

In Review ·Reported By 3 ·Updated 10 days ago

Sandbox Clone not starting due to recently deleted clone with the same name.


An issue has been found that may happen when using the sandbox cloning beta feature. If a user deletes a sandbox clone and then shortly afterwards creates a new clone with the same name and source organization the new clone may fail to progress. This occurs due to a sandbox name uniqueness error being...

In Review ·Reported By 2 ·Updated 21 days ago

[LWC Dev Experience] Datatable gets resized to default widths after certain actions

Sandbox , Lightning

Datatable gets resized to default widths after certain actions

In Review ·Reported By 3 ·Updated 28 days ago

Cannot log in to Sandbox after refresh due to multi-hour delay in user replication

Search , Sandbox

After a sandbox has been activated, it may take up to several hours for login attempts via the login portal to be successful. This is due to a delay in the replication of the user from the new sandbox environment to the redirection pointer on the test login server. In some scenarios,...

Fixed - Spring '15 Patch 11.0 ·Reported By 272 ·Updated 2019-03-22

1 to 10 of 131 | Next

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.