The response to calling Availability to get chat button availability does not contain the "isAvailable" parameter when the button is unavailable
Last updated 2022-07-27 ·Reference W-6209149 ·Reported By 1 users
When a deployment page or rest client calls Availability to get chat button availability, the response won't contain isAvailable:false as the documentation describes, when a button is unavailable.
-Configure an org with Live Agent
-Create a test chat button, and a test user with the assigned skill
-Create a test deployment page with the chat button and deployment code
-Load up the test deployment page, open the browser dev tools, and wait for the page to hit Availability.jsonp.
-When the test agent is offline, the response will not contain isAvailable, but when the agent is online, it'll contain isAvailable:true
-The same behavior occurs if Availability is hit via REST
Customers can workaround this behavior by inferring the button isn't available when isAvailable is not present in the response of the call to Availability.
Reported By (1)
Is it Fixed?
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.