Contact Center - Patch Release Notes 6.8.8

release details release date 2 feb 2026 release details this patch release for version 6 8 8 introduces significant enhancements to the omni user interface (ui) , improves backend scalability through sharding , and strengthens administrative security with a new critical alerts framework key updates also include improved 4 x to 6 x compatibility for crm and knowledge base integrations, and critical fixes for call transfer bridge integrity build and version info the following table outlines the component builds included in this release note bold entries indicate changes in this specific patch cycle component build url amf bom ocir io/bmvcldyxkwlg/amf 6 7 6 20250721 r 54847 appserver bom ocir io/bmvcldyxkwlg/appserver 6 8 43 20260129 r 264004 appserver ui bom ocir io/bmvcldyxkwlg/appserverui 6 8 12 20260120 r 261092 applite exoapplite 6 4 1 20240801 r 153309 exe art bom ocir io/bmvcldyxkwlg/art 6 8 13 20260121 r 261224 art dbquery na asrouting bom ocir io/bmvcldyxkwlg/asrouting 6 8 17 20260120 r 261079 chat service bom ocir io/bmvcldyxkwlg/chat service 6 8 22 20260120 r 261087 citus patch bom ocir io/bmvcldyxkwlg/citus patch 6 8 18 20260120 r 261089 cms bom ocir io/bmvcldyxkwlg/cms 6 8 30 20260130 r 264674 cms dbquery na crm connector bom ocir io/bmvcldyxkwlg/crm connector 6 8 18 20260120 r 261085 customer fetcher bom ocir io/bmvcldyxkwlg/cfs 6 8 20 20260120 r 261078 data engine bom ocir io/bmvcldyxkwlg/dataengine 6 8 34 20260120 r 261083 eureka bom ocir io/bmvcldyxkwlg/eureka 6 8 17 20260120 r 261084 exoxtrm ingress na fluent bit bom ocir io/bmvcldyxkwlg/fluent bit 100 0 14 20241213 r 171818 not found fluentd bom ocir io/bmvcldyxkwlg/fluentd central logger 100 0 13 20241213 r 171815 gateway bom ocir io/bmvcldyxkwlg/gateway 6 8 17 20260120 r 261081 ingress nginix controller na init na init exoxtrmutils na interaction service bom ocir io/bmvcldyxkwlg/interaction service 6 8 23 20260120 r 261086 k8tz na kafka patch bom ocir io/bmvcldyxkwlg/kafka patch 6 8 18 20260120 r 261088 logrotate(na) bom ocir io/bmvcldyxkwlg/logrotate 6 0 14 20241126 r 169000 node logcleanup bom ocir io/bmvcldyxkwlg/logcleanup k8s node 6 0 17 20241226 r 174107 postgres na postgres operator na postgresql v14 citus version v14 scheduler bom ocir io/bmvcldyxkwlg/scheduler 6 8 17 20260120 r 261082 vault na zabbix server zabbix server 7 2 0 zabbix agent zabbix agent2 7 2 0 patch bom ocir io/bmvcldyxkwlg/patch 6 8 31 20260130 r 264396 kafka kafka 2 13 3 4 1 1 x86 64 rpm redis bom ocir io/bmvcldyxkwlg/redis with modules 8 2 3 kafka connect bom ocir io/bmvcldyxkwlg/kafka connect\ v1 ksqldb(na) confluentinc/cp ksqldb server\ latest schema registry docker io/bitnami/schema registry 7 8 0 debian 12 r2 xmf bom ocir io/bmvcldyxkwlg/xtrmmessaggingframework 6 8 21 20260130 r 264676 ccdp bom ocir io/bmvcldyxkwlg/ccdp 6 8 17 20260120 r 261096 cqa bom ocir io/bmvcldyxkwlg/cqa 6 8 18 20260120 r 261094 omni ui bom ocir io/bmvcldyxkwlg/omni ui 6 8 90 20260131 r 264885 features enhancements provide option to agents to try new omni user interface (en 66) agents using the traditional gwt interface can now opt in to the new agent workspace if their selected campaigns are omni compatible benefit allows agents to transition to a modern ui (new omni ui (beta)) at their own pace without functional disruption current scope & limitations applicable to 4x and 6x gwt login flow inbound use cases only supported in this phase outbound/dialer interactions may appear but are not fully supported in omni ui configuration flag enableomninextexperience = true (stored in server preference store at contactcenter level) document https //exotel atlassian net/wiki/spaces/arch/pages/1556774925/try new ui+omninext+high level+design+hld (internal) implement off dom iframe caching for event propagation across multiple interactions (en 302) iframes retain their state and active event registrations across interaction changes, panel switches, and navigation between different tabs and apps known issue sdk events currently propagate across interactions in the debugger; this has been reported for investigation ccdp & cqa citus sharding (en 350) this update optimizes the ccdp (conversation context & data platform) to align with the citus sharding strategy , enhancing system scalability and data consistency system streamlining cqa has been decoupled and is no longer utilized on the ecc side, leaving ccdp as the primary component for distributed data management performance stability ccdp tables are now patched for sharding without impacting existing interaction summaries or downstream processes reliability post deployment validation shows zero regressions or data inconsistencies, ensuring all interaction flows function as expected istranscriptvoiceenable server preference store (en 391) this update introduces a server preference flag (isvoicetranscriptionenabled) providing granular control over call recording transcriptions cost & resource efficiency the data engine now triggers transcription requests to tasker only when this flag is active, eliminating unnecessary processing real time configuration cache eviction is now fully automated when settings change, cms publishes an event that the data engine listens to, refreshing the cache instantly zero downtime this automation removes the requirement for a data engine restart to apply new server preference configurations document links (internal) https //exotel atlassian net/wiki/spaces/ecc/pages/1688862721/poa+for+applying+ccdp+patch https //exotel atlassian net/wiki/spaces/ecc/pages/1659043852/release+upgrade+activity dialer with interaction service in backend 4 x (en 147) starting from v6 8 7 , the interaction service now manages interaction creation for auto dial calls across both 6x and 4x → 6x (harmony mode) flows scope & capabilities expanded support supports interaction creation for auto dial calls in the 6x ui (controlled via a dedicated server preference flag) and 4x → 6x flow using existing isharmonymode() flag preview dialer integration for preview dialing, an interaction record is generated as soon as the agent accepts and initiates the call data downstream captured interaction data is fully accessible for subsequent workflows and reporting key limitations preview dialer interactions are not created if a call is rejected directly from the preview popup interaction creation depends on correct configuration of server preference flags valid call id availability during interaction updates behavior for other dialer types (e g , predictive dialer ) follows existing logic and is not changed this feature focuses only on interaction creation ; reporting and analytics validation is out of scope document https //exotel atlassian net/wiki/spaces/ecc/pages/1566900244/selective+interaction+creation+by+call+type (internal) dialer with interaction service in backend 4 x & 6x oubound voice campaign || dialer in omni uad ( en 161) (en 184) interaction creation is now enabled for auto dial calls across both 6 x and 4 x–6 x environments 6 x configuration a dedicated configuration flag has been introduced to give administrators specific control over this behavior in the 6 x environment 4 x–6 x integration the system leverages the existing isharmonymode() flag to trigger interaction creation known issue users may notice that the "preview" option disappears from the interaction tab if they navigate to any other tab besides "interaction" ( ref en 755 ) restrict default ivr for transfer for campaign in /app ( en 246) this update addresses the issue where the "default ivr" option was previously visible to agents during all call transfers, regardless of the campaign type this visibility often led to accidental or incorrect selections by agents precise ui controls a new server preference flag, adddefaultivrfeaturecontextsforcampaign, has been introduced to manage the visibility of the default ivr option default behavior the default ivr remains visible for inbound campaign transfers unless it is specifically disabled through configuration flexible configuration administrators can set this flag at the contact center (cc) level for global application or at the individual campaign level override logic campaign level settings take priority and will override any global cc level configurations operational stability this change only affects the ivr list displayed in the ui; core call transfer and routing functionalities remain completely unchanged documentation https //exotel atlassian net/wiki/spaces/arch/pages/1038712881/configurable+default+ivr+in+transfer+context (internal) critical admin alerts for high impact actions (en 143) this feature introduces a platform wide critical alerts framework to prevent accidental execution of irreversible admin actions for destructive operations (such as deleting processes, campaigns, users, routing rules, or media resources), admins are shown a mandatory warning modal followed by password re authentication before the action can proceed the framework is reusable and consistent across 4x, 6x, omni, voicebot, and chatbot , with all critical actions validated at both ui and backend levels and fully audit logged this improves system safety, reduces misconfigurations and outages, and enhances traceability of high risk administrative actions noise suppression on gwt webrtc sdk (en 290) this spike introduces basic noise cancellation for agent audio on the gwt ui , enabled automatically via a backend configuration with no ui changes or agent actions required when enabled, outgoing agent audio uses lightweight noise suppression while preserving existing webrtc behavior, with a safe fallback to default audio if unsupported configuration flag a new flag disablewebrtcnoisesuppression is introduced in the server preference stor e at contactcenter level setting the value to false enables noise suppression current scope & limitations supported only on 4x and 6x gwt (webrtc) ui not supported on 4x voice toolbar, 6x voice toolbar, 4x→6x react ui, or 6x omni react ui no agent level toggle or ui control no impact on existing webrtc call flows 4 x appsdk support in omni uad (en 178) this feature enables agents logged into 6x omni ui to access apps configured for their 4x campaigns by mapping 4x app locations to corresponding 6x omni ui slots location mapping workbench sidebar (4x) → right bar (6x) topbar global (4x) → left panel (6x) workbenchinternal tab (4x) → right bar (6x) background app (4x) → right panel (6x, shown as 1px × 1px) scope & limitations applicable only for agent persona apps admin/supervisor apps are out of scope background apps are not natively supported in omni ui; temporarily rendered in the right panel partial app support; several apps are not picked, blocked, or deferred at least one 4x sdk api and event must be verified as part of validation notes 1 agent persona apps were tested dial user app and voice log privilege app are not delivering 2\ currently delivering apps are agent self monitoring , pick call app , notification app , and missed call app 3\ validation performed using 4x sdk (api & event) document https //docs google com/spreadsheets/d/1wt s7rtvkdg6m6attyxer5q5bsopocojou3p1clonwk/edit?gid=1774375378#gid=1774375378 (internal) kb url support in 6x for 4x customer 4 x and 6 x both (en 63) harmony 6x now supports a configurable landing page to enable knowledge base (kb) integration for 4x customers based on tenant level configuration, the landing page can load either the knowledge base (embedded via iframe with sso and required query parameters) or a superset dashboard , while maintaining backward compatibility for 6x customers if no configuration is applied, knowledge base is shown as the default landing page note 1 landing page behavior is driven by the end interaction landing page flag 2\ default behavior kb is loaded when no flag is configured document https //exotel atlassian net/wiki/spaces/ 7120206a5054b6882a44d2b06a4b706903a845/pages/1715601412/4x+to+6x+kb+page+nd+crm+reload (internal) crm integration sync (4x → 6x) (en 67) crm configuration from 4x is automatically detected and synced to 6x , ensuring agents get the same crm first experience post migration the crm loads as an iframe tab , auto focused for 4x tenants, with all 4x parameters, sandbox settings, and static db configs preserved call flow, customer save, and disposition work as expected flags used shouldsandboxcrmiframe = true → applies sandbox attributes to crm iframe addcustomerinfotocrmurl = true → passes customer/context details in crm url current scope & limitations applicable only to 4x migrated tenants masking flag not tested (out of scope) graceful fallback if crm config is missing future enhancements may allow role/campaign based default tab control document https //exotel atlassian net/wiki/spaces/ 7120206a5054b6882a44d2b06a4b706903a845/pages/1715601412/4x+to+6x+kb+page+nd+crm+reload (internal) omniapp || interaction timeline capture with 4 x appserver and interaction service (en 9) the interaction timeline will capture all activities from the 4 x appserver and push them to the interaction service, which manages both open and closed timelines with full lifecycle tracking data integrity, correct interaction id mapping, chronological order, and reliable delivery are ensured interaction service 403 (en 355) an intermittent 403 error was observed in the interaction service when switching between 4 x and 6 x agent logins while accessing the closed interactions ui the issue occurred due to cache data mismatch , where stale or mixed cache entries were not cleared correctly between user sessions, causing interaction apis to fail with authorization errors the issue has now been fixed by correcting cache handling and session isolation , ensuring that interaction apis respond correctly regardless of prior login context validation confirms the issue is resolved and no further occurrences were observed call transfer bridge issue customer leg incorrectly removed when first agent disposes call (en 345) during call transfers where, after a call was transferred to another campaign, disposing the call by the first agent incorrectly removed the customer leg from the bridge this resulted in loss of communication between the customer and the second agent who had already received the transferred call the issue has been fixed to ensure that only the transferring agent’s leg is disconnected upon disposal , while the customer remains connected with the second agent bridge integrity is now correctly maintained throughout the call transfer flow api for accountdb creation for new services (en 243) current behaviour (up to 6 8 6) account based databases were created only when a new contact center was created when onboarding a new service in the 4 x ↔︎ 6 x architecture for existing accounts , the required account based databases were not created automatically as a result, the account based database was created only during new contact center creation , not during service onboarding for existing accounts new behaviour (from 6 8 7 onwards) when onboarding any new service , the system now ensures that account based databases are created for existing accounts as well , if they do not already exist this guarantees database availability and consistency across all services in the 4 x ↔︎ 6 x architecture , regardless of whether the contact center is newly created or pre existing database naming convention associated databases are created using the following format \<dbname> \<ccname with unique id> \<accountid> examples interaction db mohit cc4b4a7e7a fu1rkhrmrib1fbfy data db mohit cc4b4a7e7a fu1rkhrmrib1fbfy cms redirection to 4x appserver (en 170) a new feature has been introduced to enable seamless compatibility between 4 x applications and the 6 x ui (uad 3 0) with this enhancement, the cms /app/locationinfo/appsinlocations api now intelligently redirects requests to the 4 x appserver when a 4 x user logs in via the 6 x ui this feature ensures automatic redirection of cms requests to the 4 x appserver for 4 x users accurate retrieval and rendering of 4 x app configurations within the 6 x ui smooth access to existing 4 x configured applications without any reconfiguration supported slot mapping (4 x → 6 x) workbench sidebar (4 x) → right bar (6 x) topbar global (4 x) → left panel (6 x) workbench internal tab (4 x) → right bar (6 x) background app (4 x) → right panel (6 x) this feature enables configured 4 x applications to open successfully in uad 3 0 , improving backward compatibility and ensuring a consistent agent experience omniui implement iframe persistence for left panel apps and superset dashboard (en 159) as an agent using the omninext ui , iframes in left panel apps, knowledge base, and superset dashboard now maintain their state and avoid reloading when navigating between different sections this enables seamless workflow continuity without losing context or waiting for iframe reloads verified persistence areas knowledge base page home page (superset dashboard – 6x) interaction tab (apps shown during active interactions in the right panel) note in both 4x and 6x , iframe persistence is not supported for view customer / preview dial on the interaction tab persistence is applicable only during active interactions , as discussed with the team ability to connect with ccdp apis from app sdk (en 292) from v6 8 8 , the app sdk now supports connectivity with ccdp microservice apis , enabling sdk developers to consume and exchange conversation insights and intents directly from ccdp for use within apps what’s enabled ccdp added as a supported microservice in invokeeccapi support for get and post ccdp apis via omni sdk enables publishing interaction events and fetching customer journeys works via omni toolbar (harmony cx platform) and 6x debugger app outcome app developers can seamlessly integrate ccdp data into their applications using the existing sdk framework document https //exotel atlassian net/wiki/spaces/ 7120206a5054b6882a44d2b06a4b706903a845/pages/1717469587/ability+to+connect+with+ccdp+apis+from+app+sdk (internal) dumping of aq user and campaign user ready and autocall history tables on data engine ( ga 18) from v6 8 7 , dumping of agent and campaign ready/autocall history tables to appserver and data engine is now flag controlled to address data lag issues observed earlier what’s improved eliminates multi day lag in history tables on data engine enables or disables dumping independently on appserver and data engine applies to the following tables aq user ready history aq user autocall history campaign user ready history campaign user autocall history outcome better control, reliability, and consistency of historical data supports flexible configuration based on operational needs document https //exotel atlassian net/wiki/spaces/ecc/pages/1369276418/enabling+disabling+history+tables+on+data engine+appserver+side (internal) impl of retention in all the ktables using new approach(part 1) (ga 116) impl of retention in all the ktables using new approach(part 2) (ga 117) this release introduces a new data processing approach to handle joins between two windowed datasets and persist the results in postgresql the enhancement ensures reliable data storage, improved consistency, and better control over data retention depending on the configuration, the system either joins the datasets at the streaming layer before storing them in postgresql or stores the source data first and performs the join within postgresql this improvement enhances data availability, supports accurate reporting, and improves overall system stability amcc and voicebot (en 201) (en 21) enabling agents to monitor voicebot interactions effectively, starting from an adaptive login and role selection flow to an intentional transition into active monitoring it introduces a unified agent workbench where monitoring agents can view prioritized voicebot conversations, receive critical preparatory alerts, and act with full context real time sop driven metrics and a detailed interaction view empower agents to analyze live bot conversations and intervene when required seamless takeover ensures a smooth, invisible handoff from bot to human during high risk scenarios together, these capabilities create a proactive, scalable voicebot monitoring experience that blends automation with timely human intervention note this will be delivered with a limited scope for more details, please refer to the card en 201 immediate cache expiry on 6 x service when configuration changes happen in 4 x (en 327) with this update, the services will continue to fetch configuration data from the cache as long as no changes are made on the 4 x side whenever a configuration change occurs—such as adding or deleting processes, campaigns, or users—the next api call will automatically fetch the latest configuration data the updated data is then loaded into the cache and used for subsequent requests tech tasks ga 66 / ga 71 kafka version upgrade vm as of now, the client side spring kafka library does not have a stable release for kafka client v4 1 1 as mentioned in the official documentation, older kafka client versions can communicate with newer kafka brokers/servers by negotiating a common schema version through api versioning \[ https //kafka apache org/protocol html#protocol compatibility ] therefore, this release only upgrades the kafka broker to version 4 1 1 security fixes ga 55 ||critical severity fixes for crm connector this includes package upgrades for the crm connector to fix security vulnerabilities, including tomcat and related dependencies, without upgrading spring boot scope secure package upgrades to address vulnerabilities core crm functionalities verified fetch all contact lists create and update contacts sync between remote crm and local system customer view before dial benchmarking na debugging docs / sops na monitoring task na limitations and known facts/issues with features/fixes en 142448 | for inbound calls, the popup for multiple customers does not appear in toolbar ga 14838 | filterable and searchable columns shown three times in preview alternate number list ga 14853| create and dial is not supported in toolbar in duplicate customer feature support story ga 14022 || addcustomerinfotocrmurl this flag is working only at system level only en 142553| en 140238 |saml is not supported with omni toolbar ga 14884 | bell notification not displayed after churn | preprod setup ga 14882 |toolbar || sometimes during manual dial we are facing issue invalid number ga 14851 | duplicate customer handling || mouse is shown on preview customer screen (arrow shown) ga 14843 | the call details screen under the manage tab on the supervisor interface is distorted ga 14842 |transfer to user/confer to user not able to select queue in queuelist ga 14841 | transfer to user/confer to user queuelist shown if we are going to click on campaign option ga 14534 | blacklist feature || number is only blocked if we add the zero before the number ga 14933 | data is not updating in campaign customer table after the call disposed thats why same number is dialable infinity time || third party masking setup is down ga 14932 | create and dial customer has been created successfully but calling is not working|| third party masking setup is down ga 14935 | dial time restriction setting at campaign level\ dial time is not updating in campaign customer table for the already customer ga 14937 | user disposition retry setting enabled after call disposed || campaign customer table should be updated based on setting|| issue changes are not reflecting ga 14958 | confer call icon persists after agent ends conference ga 14956 |supervisor can force logout agent without providing a reason ga 15107 | during force login the 1st user doesn't get logout properly ga 15107 fix not received ga 15100 | create a flag to persist error records in db for lead upload ga 15053 | bulk user upload users face issues during upload if the column names or their sequence are changed in the downloaded csv file, even after mapping the columns correctly during upload ga 15098 | non dialable | not working with callback ga 14935 | dial time restriction setting at campaign level\ dial time is not updating in campaign customer table for the already customer en 132681 | excluded disposition feature is not working on supervisor under manage contacts en 141977 || disabled filter at system level is working en 140367 || a filter created at the system level and not assigned to a campaign is still applied to all campaigns (legacy) ga 15223 |callback upload from supervisor during upload, if is self callback is false, then the userid being passed should be bypassed instead of failing due to a user id mismatch ga 15224| callback failure logs are not available in the app server logs to identify why the calls failed ga 15235 | callback initiate story (en 142572) || callback is not initiated if agent is logged in and agent is on break || campaign callback en 145356 |agent screen || complete contacts data column are not shown everywhere in contacts tab , in live interactions en 145173 |multiccmanager ||click on contact tab||reverting on main login screen||not able to work on contacts tab from multiccmanager en 145660 || "abandon at acd" data not dumping for chat queues when no agent is logged in || queue monitoring en 145484 || closed interactions|| search field not working with customer name ga 15313 ||customer searching issue || serachable column "name" splitted into two if we providing the name with space en 146524 || contacts tab on admin and supervisor || bulk upload || complete data columns fields are not shown for mapping en 146522 || messenger mp3 and mp4 format support issue ga 15303 || whatsapp and messenger not tested in same campaign whatsapp with xmf || chat toolbar info configured on the basis of queue|| unable to initate the whatsapp outbound chat as whatsapp business number option is not showing on ui|| due to this unable to test whatsapp and messenger in same campaign https //jira ameyo com 8999/browse/ga 15302 ||storage azure||transcript failed to send on azure if we are trying to send multiple attachement at a time from agent hr 609 outbound chat summery is not generated hr 604 past interaction count and list are not showing when the ccdp flag is enabled hr 658 || in a few conversations, the intent heading is not being generated correctly based on the interaction conversation hr 642 || case id not getting updated in journey hr 640 || a meaningful chat summary was not generated based on the agent and customer conversation hr 633 || summary sentiment does not match the interaction sentiment hr 614 || cqa scoring is sometimes not showing in the closed interaction tab under the quality profile score column hr 616 || cqa ai scoring should not be analyzed for unattended chats hr 631 || for all calls, the supervisor user should be able to perform manual scoring, whether ai scoring is conducted or not hr 646 || the screen is getting blank after creating a duplicate quality profile after switching tabs, the screen is getting refreshed hr 630 || when ai analysis is disabled, those quality profile options should not appear on the ai audit screen hr 629 || when tasker is down cqa score is showing 'no score selected' hr 628 || quality profile assignment/quality profile creation option is showing twice on screen hr 613 || the supervisor is unable to save cqa manual scoring with comments en 147340 || messages not exchanged between agent and customer after reload during ongoing chat ga 15474 || negative udh wrap time dumped in omni interaction denormalised interval 5 min for auto transferred chats ga 15421||whatsapp inbound chat ||customer name is not saving if performing inbound whatsapp chat ga 15503|| call details report || masking campaign || getting a blank report if we run the report with a phone filter either passing the mask number or unmask number ga 15452|| udh dumping issue with voice campaign and omni campaignga 47 || agents are force logged out and everything looks fine from the ameyo db side, as the logout time and reason are correctly recorded however, in live monitoring it still shows in right side but not on left side ga 110 || omni loosely coupled || customer creation failing for newly created process ga 53 | | contact and cases not displayed in crm integration tab || omni ga 155 || not getting correct graph and data in omni live monitoring ga 94||auto call on/off data points are incorrect https //exotel atlassian net/browse/gsystem disposition incorrectly displayed as "connected" when agent is force logged out during ringing statea 230|| https //jira ameyo com 8999/browse/ga 15634 ||not showing the rows per page selection option on call history page in 6 x , while it was available previously for all user roles reason \ this is to intentionally hide it, to implement cqa and ccdp flow customer reported and legacy bugs fix system common bugs na monitoring data and reports encrypted report data in the email attachment of scheduled reports (sl 17840) issue in setups where byok (bring your own key) was enabled, scheduled reports sent via email were delivered as encrypted attachments , making them unreadable to users while the report data displayed correctly in decrypted form on the ui, the email scheduler was attaching the encrypted report output files directly, leading to a mismatch between ui and emailed reports fix this issue has been resolved by ensuring that scheduled report files are properly decrypted before being attached to emails reports sent via email are now readable and consistent with the data shown on the ui current behavior after fix email scheduler csv, xls, pdf → decrypted and readable ftp / sftp csv → decrypted and readable xls, pdf → encrypted (tracked separately) resolved issue on mail with pdf,xls and csv format but on ftp and sftp getting encrypted data for xls and pdf files and decrypted in csv format separate issue open en 852 omni campaign voice and chat interactions optimization on omni ui for select campaign api and autoselectextension api (sl 17896) issue agents intermittently encountered manual dial api failures during login or call initiation the issue occurred during agent login, selectcampaign and autoselectextension apis that were triggered multiple times in parallel , creating a race condition this resulted in incomplete initialization of required listener/cache data (voicecampaign / crt objects) , causing the manual dial flow to fail fix ensured selectcampaign api is invoked only once , irrespective of single/multiple/default campaign assignments controlled autoselectextension api calls to prevent redundant execution before required data initialization completes this eliminated the race condition and stabilized manual dial behavior browser version version 143 0 7499 170 (official build) (arm64) contact / support information for issues or queries, please contact ameyo support via the support portal or designated email channels or reach out to your customer success manager