Salesforce Known Issues

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 26 ·Updated 3 days ago

Some managed package fails to upgrade in partial copy sandbox if the package contains asset file

Packaging , Sandbox , Partner

Some customers may not be able to upgrade managed package in their partial copy sandbox if the package contains asset file component. Error on the component: 1. An unexpected error occurred. Please include this ErrorId if you contact support: ... (2100495319) AssetFileName: An unexpected error occurred....

In Review ·Reported By 39 ·Updated 5 days ago

Link generated by Formula does not work correctly using "+" or "&"

Sales and Marketing , Service , Custom Objects , Sandbox , Lightning

Formula (Text) returns incorrect formula when multiple fields are referenced in combination with concactation ("+" or "&") Example Formula should generate 2 seperate hyperlinks in a field. Account Name + Opportunity Name The account name link can be used, but the opportunity name hyperlink tries...

In Review ·Reported By 4 ·Updated 6 days ago

Licenses and related storage changed in sandboxes unexpectedly.

Sandbox , Spring 20

Between Feb 1 2020 01:10 GMT and Feb 6 20:00 GMT on selected sandbox instances, Salesforce used the licenses entitlement information that existed on sandbox orgs to reapply the detailed settings. This was done to enable new settings introduced with the Spring ’20 release. For some customer sandboxes...

In Review ·Reported By 13 ·Updated 11 days ago

Default Opportunity Team Members not present in newly created sandbox.

Sales and Marketing , Sandbox , Spring 20

Due to an issue with one of the post import steps that runs during the sandbox creation process Default Opportunity Team Member records will not exist in the resulting copy.

In Review ·Reported By 1 ·Updated 14 days ago

One user not copied to clone when renaming of users results in duplicates.

Authentication , Sandbox

If the source organization of a sandbox clone has two users with similar usernames ex: Label: SFDC Test Username: Label: Main Admin Username: one of the users will be dropped when the sandbox is cloned. The system will copy both users but,...

In Review ·Reported By 3 ·Updated 19 days ago

Feature Request: Add new functionality to allow Portal or Community users to be included in Partial sandbox refresh

Custom Objects , Sandbox , User Interface

Note: This is currently classified as a Feature Request or work item that is the Salesforce internal equivalent of an Idea on the IdeaExchange. Please consider creating or promoting an Idea for this so that we may see this feature added with a future release. Existing documentation: Sandbox Setup...

In Review ·Reported By 1 ·Updated 19 days ago

Post refresh, some Sandbox copies from large Production orgs may experience issues logging in, where login page is returned on login attempt


A known issue is sometimes causing data required by the login functionality to not copied as expected, as a result post refresh when user tries to login they are returned to the login page showing "Please check your username and password. If you still can't log in, contact your Salesforce administra...

In Review ·Reported By 13 ·Updated 21 days ago

Timeout encountered during post data import step of sandbox copy process.

Sandbox , Winter 20

This is primarily meant for customers to track progress on a permanent fix after this is identified as the cause by support. Some very large sandbox copies are encountering timeouts of a query during a post data import step of the sandbox copy process. The query is run to break a job down into chunks...

In Review ·Reported By 1 ·Updated 24 days ago

Deploying Changes to the list values of Support process does not reflect on the same Record Type

Custom Objects , Metadata , Sandbox , Change Sets , Listviews , Winter 20

After deploying the support process from one org to another Org and then making changes to the support process and redeploying it with the same record type. The destination org still holds the old values rather having the updated values.

In Review ·Reported By 9 ·Updated 25 days ago

1 to 10 of 167 | 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.