Salesforce Known Issues
Trailblazer Community

"Else Approve Record" Option is Unexpectedly Rejecting Records

Platform , Workflow

The “else Approve Record” option for Approval Processes only works if it’s specified on Step 1 of an Approval Process. When this option is specified in a subsequent Step, it automatically Rejects records instead of Approving them.

In Review ·Reported By 261 ·Updated Yesterday

Email Alert sending to all members of Queue and Queue email when "Send Email to Members" is not checked

Workflow

When an approval process updates the Record Owner to a Queue and sends out an Email Alert to the Record Owner, it is sending to each individual member of the queue and the queue email itself. This should not send out an email to them because the "Notify Assignee" and "Send Email to members" of queue...

In Review ·Reported By 245 ·Updated 2 days ago

Unable to Deploy Field Update on Person Account Record Type

Workflow , Change Sets

When deploying a field update on Person Account Record Types through Change Set and it is failing with error "In field: lookupValue - no RecordType named Account.Record_Type_Name found"

In Review ·Reported By 47 ·Updated 2 days ago

Duplicate FeedItem is created when the IsPublished field is updated by Automated Process when adding a new Case Comment

Service , Workflow

Duplicate FeedItem with Type "CaseCommentPost" is created when the value of isPublished is updated in same transaction by automated process such as Workflow rule and Process while adding new Case comment.

No Fix ·Reported By 0 ·Updated 4 days ago

Field Updates by Flow or Process are not triggering Case Escalation Rules

Service , Workflow , Flow , Process Builder

Case escalation rules are not being properly reevaluated after process/flow invoked field updates. Per Order of Execution doc (https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm) escalation rules are to evaluate after Workflow and Process...

In Review ·Reported By 56 ·Updated 8 days ago

Approval history related list for lightning knowledge article's translation shows entry for Translation

Workflow , Knowledge , Lightning

In Lightning Knowledge, when a user sends an article for translation an internal ProcessInstanceWorkitem row is automatically generated by the State-based ProcessDefinition: KBTranslationSubWorkflow. Documentation indicates, "State-based Process—Used internally to track various control processes,...

In Review ·Reported By 21 ·Updated 10 days ago

Workflow does not use current value for "Owner:Queue.QueueName" in recursive evaluation if Owner was changed in prior evaluation.

Workflow

Workflow formula criteria referring to "Owner:Queue.QueueName" uses the Queue Name as of the start of the workflow evaluation, even in a recursive evaluation after the owner is changed.

In Review ·Reported By 15 ·Updated 10 days ago

Outbound message notifications are not sent when there's outbound message having failed for more than 24 hours.

Workflow

Outbound message notifications are not sent when there's outbound message having failed for more than 24 hours.

In Review ·Reported By 5 ·Updated 10 days ago

Updating percentage fields with process builder using a referenced value from a percent formula field in the parent object produces incorrect value

Platform , Workflow , Process Builder

Updating percentage fields with process builder using a referenced value from a percent formula field in the parent object produces incorrect value

In Review ·Reported By 21 ·Updated 16 days ago

Feed Post not visible after User creates a record using a Quick Action if Process updates a field on the record

Workflow , Process Builder

Feed Post not visible after User creates a record using a Quick Action if a Process/Workflow updates a field on the record.

In Review ·Reported By 86 ·Updated 17 days ago

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