Genesys Cloud - Main

We noticed that the maximum number of queues that can be selected in a queue view (activity/performance) is limited to 150. Is this a hard limit or is there a way to increase this number ?
#Reporting/Analytics

------------------------------
Fabiano Benedetti
NTT Belgium NV/SA
------------------------------

This is a hard limit.  Those views update with realtime notifications with each queue being added contributing to an additional realtime subscription.  If we went above 150, users could start to lose realtime subscriptions elsewhere like chat notifications, user's online status, inbox notifications, etc.  Pumping in data to the browser in realtime for more than 150 queues at once can also make user's browsers struggle to receive that much information.  That could lead to higher minimum machine spec requirements, higher bandwidth requirements, slow application experience, or failure to load the view at all.

------------------------------
Ryan Legner
Staff Product Manager, Genesys Cloud CX
------------------------------

Hi Ryan, 

Should the 150 limit be automatic or that has to be set? Currently Genesys will only allow us 100 queues. 

------------------------------
Anna Jhane Mulinyawe
Accenture LLP
------------------------------

Original Message:
Sent: 01-11-2023 09:47
From: Ryan Legner
Subject: Queue Views (activity/performance) : maximum number of queues in filter

This is a hard limit.  Those views update with realtime notifications with each queue being added contributing to an additional realtime subscription.  If we went above 150, users could start to lose realtime subscriptions elsewhere like chat notifications, user's online status, inbox notifications, etc.  Pumping in data to the browser in realtime for more than 150 queues at once can also make user's browsers struggle to receive that much information.  That could lead to higher minimum machine spec requirements, higher bandwidth requirements, slow application experience, or failure to load the view at all.

------------------------------
Ryan Legner
Staff Product Manager, Genesys Cloud CX
------------------------------

Exactly, I am getting the Queue Limit Reached when only selected 100 queues in Queue Performance view. Not sure why it is not set at 150.

------------------------------
John Chan
FLIGHT CENTRE TRAVEL GROUP LIMITED
------------------------------

Original Message:
Sent: 09-20-2023 15:27
From: Anna Jhane Mulinyawe
Subject: Queue Views (activity/performance) : maximum number of queues in filter

Hi Ryan, 

Should the 150 limit be automatic or that has to be set? Currently Genesys will only allow us 100 queues. 

------------------------------
Anna Jhane Mulinyawe
Accenture LLP
------------------------------


Original Message:
Sent: 01-11-2023 09:47
From: Ryan Legner
Subject: Queue Views (activity/performance) : maximum number of queues in filter

This is a hard limit.  Those views update with realtime notifications with each queue being added contributing to an additional realtime subscription.  If we went above 150, users could start to lose realtime subscriptions elsewhere like chat notifications, user's online status, inbox notifications, etc.  Pumping in data to the browser in realtime for more than 150 queues at once can also make user's browsers struggle to receive that much information.  That could lead to higher minimum machine spec requirements, higher bandwidth requirements, slow application experience, or failure to load the view at all.

------------------------------
Ryan Legner
Staff Product Manager, Genesys Cloud CX

Hi @Ryan Legner we are seeing this limit at 101 itself, or anything we can do to reach 150 objects in filter condition. 

is it the same limit of 100 objects, even if someone use API/SDK to fetch the data ?  Thank you !

------------------------------
Hanumantha Rao
------------------------------

Original Message:
Sent: 01-11-2023 09:47
From: Ryan Legner
Subject: Queue Views (activity/performance) : maximum number of queues in filter

This is a hard limit.  Those views update with realtime notifications with each queue being added contributing to an additional realtime subscription.  If we went above 150, users could start to lose realtime subscriptions elsewhere like chat notifications, user's online status, inbox notifications, etc.  Pumping in data to the browser in realtime for more than 150 queues at once can also make user's browsers struggle to receive that much information.  That could lead to higher minimum machine spec requirements, higher bandwidth requirements, slow application experience, or failure to load the view at all.

------------------------------
Ryan Legner
Staff Product Manager, Genesys Cloud CX
------------------------------

Limits on the amount of objects to apply in your query filter are documented here.  https://developer.genesys.cloud/organization/organization/limits#analytics-api  They'll be referred to as "predicate" limits where a predicate is the amount of filter criteria you can put into your API query.  More objects can be filtered, but would have to be spanned across multiple queries.  Whether that will work for your use case depends on the design of the application and the needs it must meet.

------------------------------
Staff Product Manager, Genesys Cloud CX
Genesys - Employees
------------------------------

Original Message:
Sent: 02-04-2025 08:34
From: Hanumantha Rao
Subject: Queue Views (activity/performance) : maximum number of queues in filter

Hi @Ryan Legner we are seeing this limit at 101 itself, or anything we can do to reach 150 objects in filter condition. 

is it the same limit of 100 objects, even if someone use API/SDK to fetch the data ?  Thank you !

------------------------------
Hanumantha Rao
------------------------------


Original Message:
Sent: 01-11-2023 09:47
From: Ryan Legner
Subject: Queue Views (activity/performance) : maximum number of queues in filter

This is a hard limit.  Those views update with realtime notifications with each queue being added contributing to an additional realtime subscription.  If we went above 150, users could start to lose realtime subscriptions elsewhere like chat notifications, user's online status, inbox notifications, etc.  Pumping in data to the browser in realtime for more than 150 queues at once can also make user's browsers struggle to receive that much information.  That could lead to higher minimum machine spec requirements, higher bandwidth requirements, slow application experience, or failure to load the view at all.

------------------------------
Ryan Legner
Staff Product Manager, Genesys Cloud CX