Salesforce Known Issues
Trailblazer Community

User with “Manage Sandboxes” permission cannot refresh sandbox via Tooling API without “Modify All Data“ permission

Apex , API

When a user has “Manage Sandboxes” permission, but does not have “Modify All Data” permission, they cannot refresh a sandbox via Tooling API using PATCH method on SandboxInfo object. Note that the user can refresh the sandbox via UI.

In Review ·Reported By 9 ·Updated 4 days ago

QueriedEntities on ReportEvent does not always contain all the queried entity types

Apex , API , Platform

ReportEvent Policy part of enhanced transaction security policy doesnt always show correct values for the condition/attribute QueriedEntities.

Fixed - Winter '21 ·Reported By 7 ·Updated 4 days ago

Retrieving Quick Action does not provide <formula> for <fieldOverrides> in the exported file

API

Retrieving a Quick Action with a predefined field does not provide <formula> for <fieldOverrides>. As the retrieved metadata doesn't include the formula, deploying the retrieved metadata to another org throws an error :"required fields are missing: [DefaultValueFormula]"

Fixed - Winter '21 ·Reported By 6 ·Updated 4 days ago

Order Management invocable action errors are not propagated back to the caller

API , Flow , Commerce Cloud Order Management

**This issue is related to Salesforce Order Management Only*** If status of Order is 'Activated' when attempting to cancel item from using cancel item flow on the order summary will result in the following generic error. Error: [xmlrpc=-1, statusCode=UNKNOWN_EXCEPTION, exceptionCode=UNKNOWN_EXCEPTION,...

Fixed - Winter '21 ·Reported By 6 ·Updated 4 days ago

Internal Server exception (Error ID: 303983350-111323 (-1223908915)) while Validating from the External Objects list in External Data Sources.

API

- An internal server error is being thrown when validating External Objects after syncing with the external data sources. - The issue is occurring only in Spring '20 orgs. In Winter'20 orgs no error is seen. - The issue is also replicable using the URL (http://orderdb.herokuapp.com/orders.svc/)...

Fixed - Spring '20 Patch 6.0 ·Reported By 6 ·Updated 4 days ago

DescribeSObject should reflect the length of dynamic picklist fields on Standard entities correctly (current behavior always defaults to 40)

API

When describing a standard entity via describeSObject, picklist fields should return the actual maximum length (usually 255). Currently, they always return length=40. This can cause issues for 3rd parties who rely on the results of DescribeSObject to determine the maximum allowed length for a fie...

Fixed - Spring '20 Patch 4.0 ·Reported By 6 ·Updated 4 days ago

Case can have multiple Public Draft Emails related at a time via API Insert

Activities , API , Service

Customers may observe that multiple Email Message records in Draft Status can be related to a Case record at a time when inserted via the API. Only 1 Email Message record in Draft Status should be permitted to be related to a Case at a time per the following documentation: Classic: https://help.salesforce.com/articleView?id=case_interaction_draft_emails.htm&type=5 Lightning:...

In Review ·Reported By 5 ·Updated 4 days ago

Feed Comments that were migrated may appear out of order when "Allow Discussion Threads" Community Preference is enabled.

API , Chatter , Communities

Feed Comments related to a Feed Post may not appear in chronological order if they were inserted via the api as a part of a migration. This occurs if the preference "Allow Discussion Threads" is enabled in any Community(Active, Inactive, or in Preview). It will affect the sort order in any Community...

In Review ·Reported By 5 ·Updated 4 days ago

Error when querying Custom Formula Field on ArticleTotalViewCount field

API , Operational Analytics - Reports

An error is returned when querying Custom Fields that reference the ArticleTotalViewCount field. This occurs whether the query takes place through the UI (Reports), or API.

Fixed - Spring '21 ·Reported By 5 ·Updated 4 days ago

Chat API endpoint /chat/rest/Chasitor/ChatMessage results in 500 error if called in quick succession

API , Mobile , Live Agent , Omni-Channel

Chat API endpoint /chat/rest/Chasitor/ChatMessage results in Error 500: An error has occurred while processing your request. The salesforce.com support team has been notified of the problem. Error ID: 1460560579-917 (-1292368750)

No Fix ·Reported By 5 ·Updated 4 days ago

Prev | 21 to 30 of 524 | 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.