Known Issues · Omni-Channel
When a user that belongs to a Call Center is viewing the Agents tab in Omni Supervisor in Classic console, they will see a gray background image in the Status column
In Review ·Reported By 2 ·Updated Today
When an available agent is assigned work and logs into Omni from another browser just at the same moment, that work may not be transferred to the new session. When this happens, the AgentWork record remains stuck in 'assigned', the work record itself remains owned by the agent, and the work will not...
In Review ·Reported By 3 ·Updated Yesterday
Agents who use the transfer to agent feature for Live Agent/Omni-Channel Chats will notice that if the transfer times out and is returned to them, then duplicate entries will show in the Omni Supervisor Panel. No actual duplicate chats are created from this event as it is isolated to the Omni Supervisor...
In Review ·Reported By 1 ·Updated Yesterday
Duplicate Rules that are set up to allow duplicate record creation are causing issues with Snap-Ins Prechat that is supposed to create records. Intermittently these records will not create in their org.
In Review ·Reported By 2 ·Updated 6 days ago
While utilizing Omni Skills Based Routing in Classic Console, agents may find themselves seeing an internal server error occurring. The chat connects successfully but the agent cannot respond to the customer.
In Review ·Reported By 12 ·Updated 7 days ago
Lightning Console chats my sometimes not display the auto greeting set up via configuration. This is due to a race condition where the auto-greeting is sending before the chat log has loaded, therefore it will not render correctly.
In Review ·Reported By 8 ·Updated 9 days ago
PendingServiceRouting is getting deleted when the case owner changed from user to queue & SBR is enabled
Fixed - Summer '19 ·Reported By 23 ·Updated 12 days ago
Triggers, flows, and processes fail when the Automated Process user attempts to access AgentWork.OriginalQueueId field.
Fixed - Summer '19 ·Reported By 8 ·Updated 12 days ago
When we enable snaps-ins in an org and add the snap-ins to a lightning community and then validate the HTML after parsing the Js in the Validator.w3.org we see errors.
Fixed - Summer '19 ·Reported By 1 ·Updated 12 days ago
The ServiceResource/ServiceResourceSkill objects are not seen on Classic setup tree if Field Service Lightning is disabled and Omni Skill-Based Routing is enabled.
Fixed - Summer '19 Patch 2.0 ·Reported By 0 ·Updated 12 days ago
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.