# Troubleshooting Webex WFO data gaps for Webex Contact Center Canonical: https://warmtransfer.net/knowledge/wxcc-wfo-troubleshooting Last verified: 2026-10-02 Webex WFO connects to Webex Contact Center through an ACD connection that synchronizes users, teams and service queues on a configurable interval[^53]. Historical data from Webex Contact Center may not be available to the WFO platform for up to 120 minutes after an interval ends[^21]. ## How the connection moves data The Webex Contact Center 2.0 ACD connection has a User Sync setting that enables synchronization of user data into the WFO platform from Webex Contact Center[^56]. The Synchronization Interval (Minutes) field sets how often users, teams and service queues are synchronized with their Webex Contact Center equivalents[^53]. The Capture Delay (minutes) field sets how long WFM waits before it imports ACD statistics[^12]. The WFO connection documentation refers to Webex Contact Center as Cisco Customer Journey Platform (CJP), so the connector may be labelled CJP in the WFO platform[^13]. WFM queue and agent statistics and ready-time adherence data are updated periodically during the day, usually every 15 or 30 minutes[^52]. WFM external logons, which connect ACD statistics to agents, are populated automatically from the external system every night[^18]. After an agent's first contact, the agent's external logon only appears in WFM after waiting overnight[^17]. There is no automatic user sync between the WFM application and the QM/Analytics application, and users are managed in each[^28]. ## Connection account and authentication The Username on the Webex CC 2.0 connection should be a service-type account that is never changed, because changing the account can cause duplicate users and teams[^47]. The API user for the connection must meet these documented requirements:[^10][^8][^9] - Its role must have the Record Screen and Record Voice permissions[^10]. - It must be assigned to the Default Team on the Users page[^8]. - It must be given full scope by selecting all groups and teams under Associated Groups and Teams[^9]. OAuth token refresh failures can be caused by changing the administrator email, deactivating the account in Active Directory, password changes or switching domains, and the Authorization URL setting on an existing Webex CC 2.0 connection addresses them[^31]. The Authorization URL setting lets the system re-establish OAuth authentication after a token refresh failure for a maximum of 60 days[^30]. ## Missing or wrong users, teams and queues - **User absent in WFO.** Users with a Not Active status in Webex Contact Center are not imported into the WFO platform unless they are restored[^29]. - **Deleted user still listed.** When a user is deleted in Webex Contact Center, the synced WFO user is deactivated rather than deleted[^15]. - **Agent role returns after removal.** If the agent role is removed from a WFO user synced with a contact-center-enabled Webex CC user, the agent role is reassigned at the next sync[^5]. - **Team missing.** The connection syncs Webex CC teams of any type, Capacity Based or Agent Based, as long as they are active[^55]. - **Team membership empty.** The connection does not preserve the relationship between Webex CC users and Webex CC teams, so users must be reassigned to teams manually in the WFO platform[^54]. - **Queue missing.** The connection syncs Webex CC Queues and Outdial Queues as service queues[^38]. - **Duplicate users and teams.** Changing the connection Username account can cause duplicate users and teams[^47]. When adding WFM agents manually, entering an email address as the WFM logon immediately triggers an email to the user, so the address should not be entered until the agent is ready to access the system[^16]. An agent's WFM time zone controls how they view shifts and staffing, and rather than editing it after creation, the agent should be terminated and recreated with the correct time zone[^6]. ## Queue statistics and forecasting gaps Creating a WFM workload requires queue data, either through access to queues via an integration or a queue data file to import[^58]. For a new installation, WFM documentation directs importing historical queue data to base a forecast on[^22]. The WFM queue data import file supports interval lengths of 15, 30 and 60 minutes[^36]. The file must be UTF-8 CSV or TXT without column headers, sorted chronologically by date and time, with all fields present in order and 0 entered for missing values[^35]. When creating a WFM skill, the time zone is usually set to where the workload is, or to where the resource planners are if the workload covers several time zones[^49]. For a skill time zone whose UTC offset is not a full hour, the interval length must allow alignment to full hours: 15 or 30 minutes for UTC+5:30 and 15 minutes for UTC+5:45[^32]. To check imported figures, the WFM Queue Statistics report shows raw queue data per interval and is intended to validate WFM queue statistics against the ACD platform[^37]. The WFM Agent Queue Statistics report shows raw agent data bound to queue per interval, to validate WFM agent statistics against the ACD platform[^4]. Before treating a recent interval as missing, allow for the documented delay of up to 120 minutes after an interval ends[^21]. ## Adherence gaps WFM adherence overviews and reports always use state groups, never the individual ACD states[^51]. New states that arrive from the ACD and have not been configured are added to the default state group and must be moved manually[^27]. Changes to adherence state group settings can take up to 20 minutes to take effect[^50]. Historical adherence percentage is total time in adherence divided by total work time minus total neutral periods, multiplied by 100[^2]. The historical adherence percentage is shown when the shift has ended and covers the full shift even when the shift crosses midnight, while ongoing shifts show adherence from shift start until now[^3]. States that arrive before or after the scheduled shift do not affect the historical adherence score[^33]. ## Granular agent states and RTA interruption Webex WFO introduced an enhanced WFM adherence connector, integrating with a new Webex webhook, to support Webex CC granular agent states[^1]. Once granular agent states are enabled, existing WFO state grouping configurations no longer align with the new multi-channel agent states, and RTA reporting is interrupted unless state groupings were reconfigured using the new adherence connector[^46]. From April 30, 2026, the tenant-level admin toggle for granular agent state control is available in Control Hub for 6 months, until October 29, 2026, after which granular state control goes to general availability for all agents[^20]. The Webex CC agent states article instructs tenants to keep the granular agent state admin toggle off in Control Hub to continue using Webex WFO[^24]. Webex CC granular agent states are scheduled to roll out to all Webex CC customers on October 29, 2026[^19]. ## Recording gaps For a single user not recording, the documented checks are user permissions, assignment to a phone, membership of a team configured for recording in a workflow, recording inclusion or exclusion lists, and phone configuration on the telephony side[^48]. When recording is down for all users, the documented checks are telephony monitoring status, signalling in the data server logs and free space on the capture servers, with a service restart possibly required if servers do not show as connected[^7]. Automated Contact Reconciliation compares contact records between Webex Contact Center and Webex WFO to identify missing or incomplete recordings and initiates recovery[^39]. It runs as a daily process that scans contact record data from the past 25 hours[^40]. It is disabled by default and is activated by request through the Cisco Customer Success Manager or support contact[^41]. Manual contact recovery requests have these documented constraints:[^45][^42][^44][^43] - The contact recovery request page is available only to cloud users who are tenant administrators[^45]. - A request can only target recordings no more than 36 months old[^42]. - Each user can have up to 5 pending requests[^44]. - Requests cannot be scheduled for future dates, and require the integrated platform to be running with the underlying cause of the missing recordings resolved[^43]. Contacts must be less than a year old to appear in a user's QM contact queue, even when assigned by an ad-hoc task[^14]. ## Documentation currency The Webex WFO and Webex Contact Center Integration Guide with New WFM listed on Cisco's Webex WFO support page is dated 20 January 2022[^23]. ## See also - [Provisioning Webex WFO workforce management and quality management for Webex Contact Center](https://warmtransfer.net/knowledge/wxcc-wfo-provisioning-setup) - [Webex Contact Center workforce optimization and recording](https://warmtransfer.net/knowledge/webex-cc-wfo) - [Webex Contact Center RONA and agent state handling](https://warmtransfer.net/knowledge/webex-cc-rona-agent-state) - [Webex Contact Center queues teams and routing strategies](https://warmtransfer.net/knowledge/webex-cc-routing) - [Webex Contact Center APIs and webhooks](https://warmtransfer.net/knowledge/webex-cc-apis) ## Applicability The Basic WFM offering on Webex WFO for Webex Contact Center includes real-time adherence management alongside forecasting across voice, digital and back-office channels[^11]. The granular agent state toggle window runs from April 30, 2026 to October 29, 2026[^20]. The contact queue age limit is documented on the classic contact queue page[^14]. Applies to: Calabrio ONE, Calabrio WFM, Cisco Webex WFO, Calabrio QM, and Cisco Webex Contact Center. Deployments: multi-tenant. Sources checked 2026-10-02. ## What remains uncertain The content of the Webex WFO Webhook Change Preparation Guide is not covered by the sources below. The admin toggle for granular agent state control is available until October 29, 2026, after which granular state control goes to general availability for all agents[^20]. Whether WFO tenants can still hold off granular agent states after that date is not covered by the sources below. Unconfigured new ACD states are added to the default state group[^27]. How Webex CC idle codes and per-channel states arrive as ACD states in new WFM is not covered by the sources below. The automatic history backfill period when the Webex CC connection is created is not covered by the sources below. The time zone in which Webex CC queue statistics are registered in WFM is not covered by the sources below. The timing semantics of the immediate and off-peak contact recovery options are not covered by the sources below. Whether the CJP connection documentation still applies to tenants on the 2.0 connector is not covered by the sources below. An explicit source for the relationship between Webex WFO documentation and any upstream platform documentation is not covered by the sources below. ## Sources [^1]: Webex WFO introduced an enhanced WFM adherence connector, integrating with a new Webex webhook, to support Webex CC granular agent states. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated July 22, 2026, 'Webex WFO: WFM - Adherence Connector Enhancement for Granular Agent States'. Checked 2026-10-02. [^2]: Historical adherence percentage is total time in adherence divided by total work time minus total neutral periods, multiplied by 100. Source: [About historical adherence](https://wfohelp.com/doc/Content/user-guides/adherence/about-historical-adherence.htm), section on calculation. Checked 2026-10-02. [^3]: The historical adherence percentage is shown when the shift has ended, and covers the full shift even when the shift crosses midnight; ongoing shifts show adherence from shift start until now. Source: [About historical adherence](https://wfohelp.com/doc/Content/user-guides/adherence/about-historical-adherence.htm), page body, display and midnight paragraphs. Checked 2026-10-02. [^4]: The WFM Agent Queue Statistics report shows raw agent data bound to queue per interval, to validate WFM agent statistics against the ACD platform. Source: [WFM standard reports](https://www.wfohelp.com/doc/Content/user-guides/wfm-reports/about-wfm-reports.htm), report table, Agent Queue Statistics row. Checked 2026-10-02. [^5]: If the agent role is removed from a WFO user synced with a contact-center-enabled Webex CC user, the agent role is reassigned at the next sync. Source: [Connection settings for Cisco Webex Contact Center](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc.htm), section 'Users'. Checked 2026-10-02. [^6]: An agent's WFM time zone controls how they view shifts and staffing, and rather than editing it after creation the agent should be terminated and recreated with the correct time zone. Source: [Add or edit WFM agents manually](https://wfohelp.com/doc/Content/user-guides/people/add-edit-agents.htm), General tab, Time zone field. Checked 2026-10-02. [^7]: When recording is down for all users, the documented checks are telephony monitoring status, signalling in the data server logs and free space on the capture servers, with a service restart possibly required if servers do not show as connected. Source: [Troubleshoot issues with recording](https://wfohelp.com/doc/Content/user-guides/troubleshooting/2024-troubleshooting-project/users-not-recording.htm), section on recording down for all users. Checked 2026-10-02. [^8]: The API user for the Webex CC 2.0 connection must be assigned to the Default Team on the Users page. Source: [Connection settings for Cisco Webex Contact Center 2.0](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc-2.0.htm), settings list, API Username requirements. Checked 2026-10-02. [^9]: The API user for the Webex CC 2.0 connection must be given full scope by selecting all groups and teams under Associated Groups and Teams. Source: [Connection settings for Cisco Webex Contact Center 2.0](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc-2.0.htm), settings list, API Username requirements. Checked 2026-10-02. [^10]: The API user for the Webex CC 2.0 connection must have the Record Screen and Record Voice permissions in its role. Source: [Connection settings for Cisco Webex Contact Center 2.0](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc-2.0.htm), settings list, API Username requirements. Checked 2026-10-02. [^11]: The Basic WFM offering on Webex WFO for Webex Contact Center includes real-time adherence management alongside forecasting across voice, digital and back-office channels. Source: [Basic WFM and QM Offerings on Webex WFO (Webex Contact Center)](https://help.webex.com/en-us/article/nmzg380/Basic-WFM-and-QM-Offerings-on-Webex-WFO-(Webex-Contact-Center)), Basic WFM feature list. Checked 2026-10-02. [^12]: The Capture Delay (minutes) field on the Webex CC 2.0 connection sets how long WFM waits before it imports ACD statistics. Source: [Connection settings for Cisco Webex Contact Center 2.0](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc-2.0.htm), settings list, field 'Capture Delay (minutes)'. Checked 2026-10-02. [^13]: The WFO connection documentation refers to Webex Contact Center as Cisco Customer Journey Platform (CJP), so the connector may be labelled CJP in the WFO platform. Source: [Connection settings for Cisco Webex Contact Center](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc.htm), page introduction note. Checked 2026-10-02. [^14]: Contacts must be less than a year old to appear in a user's QM contact queue, even when assigned by an ad-hoc task. Source: [Access contacts assigned to you (classic page)](https://wfohelp.com/doc/Content/user-guides/recordings/contact-queue.htm), page body. Checked 2026-10-02. [^15]: When a user is deleted in Webex Contact Center, the synced WFO user is deactivated rather than deleted. Source: [Connection settings for Cisco Webex Contact Center](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc.htm), section 'Users', change-mapping table row 'User is deleted'. Checked 2026-10-02. [^16]: Entering an email address as the WFM logon immediately triggers an email to the user, so the address should not be entered until the agent is ready to access the system. Source: [Add or edit WFM agents manually](https://wfohelp.com/doc/Content/user-guides/people/add-edit-agents.htm), General tab, Logon field. Checked 2026-10-02. [^17]: After an agent's first contact, the agent's external logon only appears in WFM after waiting overnight. Source: [Manage users in WFM and QM/Analytics](https://wfohelp.com/doc/Content/user-guides/people/manage-users-in-WFM-QM-Analytics.htm), section on adding users to WFM, external logon note. Checked 2026-10-02. [^18]: WFM external logons, which connect ACD statistics to agents, are populated automatically from the external system every night. Source: [Manage users in WFM and QM/Analytics](https://wfohelp.com/doc/Content/user-guides/people/manage-users-in-WFM-QM-Analytics.htm), section on adding users to WFM, external logon note. Checked 2026-10-02. [^19]: Webex CC granular agent states are scheduled to roll out to all Webex CC customers on October 29, 2026. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated July 22, 2026. Checked 2026-10-02. [^20]: From April 30, 2026 the tenant-level admin toggle for granular agent state control is available in Control Hub for six months, until October 29, 2026, after which granular state control goes to general availability for all agents. Source: [Understand agent states](https://help.webex.com/en-us/article/nvg4gu6/Understand-agent-states), section 'Manage channel-specific availability'. Checked 2026-10-02. [^21]: Historical data from Webex Contact Center may not be available to the WFO platform for up to 120 minutes after an interval ends. Source: [Connection settings for Cisco Webex Contact Center](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc.htm), section 'Capture Settings'. Checked 2026-10-02. [^22]: For a new installation, WFM documentation directs importing historical queue data to base a forecast on. Source: [Create a workload](https://wfohelp.com/doc/Content/user-guides/forecasts/create-workload.htm), steps, queue selection. Checked 2026-10-02. [^23]: The Webex WFO and Webex Contact Center Integration Guide with New WFM listed on Cisco's Webex WFO support page is dated 20 January 2022. Source: [Webex Workforce Optimization - Support](https://www.cisco.com/c/en/us/support/contact-center/webex-workforce-optimization/series.html), Install and Upgrade / integration guides listing row. Checked 2026-10-02. [^24]: The Webex CC agent states article instructs tenants to keep the granular agent state admin toggle off in Control Hub to continue using Webex WFO. Source: [Understand agent states](https://help.webex.com/en-us/article/nvg4gu6/Understand-agent-states), section 'Manage channel-specific availability'. Checked 2026-10-02. [^25]: An agent missing from Webex WFO is most likely explained, in order, by User Sync being disabled, the next sync interval not having elapsed, the agent being Not Active in Webex CC, or the agent existing in QM but not created in WFM, since these are the documented sync gates (inferred). Source: [Connection settings for Cisco Webex Contact Center](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc.htm), section 'Users', read with 2.0 page fields 'User Sync' and 'Synchronization Interval' and manage-users page introduction. Checked 2026-10-02. [^26]: A new Webex CC idle code is likely to land in the WFM default state group until an administrator moves it, producing wrong adherence for agents using that code (inferred). Source: [Group adherence states](https://wfohelp.com/doc/Content/user-guides/adherence/group-adherence-states.htm), page body, paragraph on new states. Checked 2026-10-02. [^27]: New states that arrive from the ACD and have not been configured are added to the default state group and must be moved manually. Source: [Group adherence states](https://wfohelp.com/doc/Content/user-guides/adherence/group-adherence-states.htm), page body, paragraph on new states. Checked 2026-10-02. [^28]: There is no automatic user sync between the WFM application and the QM/Analytics application; users are managed in each. Source: [Manage users in WFM and QM/Analytics](https://wfohelp.com/doc/Content/user-guides/people/manage-users-in-WFM-QM-Analytics.htm), page introduction. Checked 2026-10-02. [^29]: Users with a Not Active status in Webex Contact Center are not imported into the WFO platform unless they are restored. Source: [Connection settings for Cisco Webex Contact Center](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc.htm), section 'Users'. Checked 2026-10-02. [^30]: The Authorization URL setting lets the system re-establish OAuth authentication after a token refresh failure for a maximum of sixty days. Source: [Connection settings for Cisco Webex Contact Center 2.0](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc-2.0.htm), settings list, field 'Authorization URL'. Checked 2026-10-02. [^31]: The Authorization URL setting on an existing Webex CC 2.0 connection addresses OAuth token refresh failures caused by changing the administrator email, deactivating the account in Active Directory, password changes or switching domains. Source: [Connection settings for Cisco Webex Contact Center 2.0](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc-2.0.htm), settings list, field 'Authorization URL' (existing ACD only). Checked 2026-10-02. [^32]: For a skill time zone whose UTC offset is not a full hour, the interval length must allow alignment to full hours: 15 or 30 minutes for UTC+5:30 and 15 minutes for UTC+5:45. Source: [Create a skill](https://wfohelp.com/doc/Content/user-guides/forecasts/create-skill.htm), field description, Interval length. Checked 2026-10-02. [^33]: States that arrive before or after the scheduled shift do not affect the historical adherence score. Source: [About historical adherence](https://wfohelp.com/doc/Content/user-guides/adherence/about-historical-adherence.htm), page body. Checked 2026-10-02. [^34]: Because the toggle window ends on October 29, 2026 and granular state control then reaches all agents, Webex WFO tenants that relied on keeping the toggle off will need state groupings reconfigured on the new adherence connector to avoid RTA interruption (inferred). Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated July 22, 2026, read with nvg4gu6 section 'Manage channel-specific availability'. Checked 2026-10-02. [^35]: The queue data import file must be UTF-8 CSV or TXT without column headers, sorted chronologically by date and time, with all fields present in order and 0 entered for missing values. Source: [Queue data file format](https://wfohelp.com/doc/Content/user-guides/forecasts/about-queue-data-format.htm), file rules list. Checked 2026-10-02. [^36]: The WFM queue data import file supports interval lengths of 15, 30 and 60 minutes. Source: [Queue data file format](https://wfohelp.com/doc/Content/user-guides/forecasts/about-queue-data-format.htm), field table, interval length. Checked 2026-10-02. [^37]: The WFM Queue Statistics report shows raw queue data per interval and is intended to validate WFM queue statistics against the ACD platform. Source: [WFM standard reports](https://www.wfohelp.com/doc/Content/user-guides/wfm-reports/about-wfm-reports.htm), report table, Queue Statistics row. Checked 2026-10-02. [^38]: The WFO connection syncs Webex CC Queues and Outdial Queues as service queues. Source: [Connection settings for Cisco Webex Contact Center](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc.htm), section 'Service Queues'. Checked 2026-10-02. [^39]: Automated Contact Reconciliation compares contact records between Webex Contact Center and Webex WFO to identify missing or incomplete recordings and initiates recovery. Source: [About Automated Contact Reconciliation](https://wfohelp.com/doc/Content/user-guides/application-management/enable-automated-record-reconciliation.htm), page body, first paragraph. Checked 2026-10-02. [^40]: Automated Contact Reconciliation runs as a daily process that scans contact record data from the past twenty-five hours. Source: [About Automated Contact Reconciliation](https://wfohelp.com/doc/Content/user-guides/application-management/enable-automated-record-reconciliation.htm), page body. Checked 2026-10-02. [^41]: Automated Contact Reconciliation is disabled by default and is activated by request through the Cisco Customer Success Manager or support contact. Source: [About Automated Contact Reconciliation](https://wfohelp.com/doc/Content/user-guides/application-management/enable-automated-record-reconciliation.htm), section on enabling. Checked 2026-10-02. [^42]: A manual contact recovery request can only target recordings no more than 36 months old. Source: [Schedule contact recovery requests](https://wfohelp.com/doc/Content/user-guides/application-management/recovery-request.htm), prerequisites list. Checked 2026-10-02. [^43]: Recovery requests cannot be scheduled for future dates, and require the integrated platform to be running with the underlying cause of the missing recordings resolved. Source: [Schedule contact recovery requests](https://wfohelp.com/doc/Content/user-guides/application-management/recovery-request.htm), prerequisites and limitations lists. Checked 2026-10-02. [^44]: Each user can have up to five pending manual contact recovery requests. Source: [Schedule contact recovery requests](https://wfohelp.com/doc/Content/user-guides/application-management/recovery-request.htm), limitations list. Checked 2026-10-02. [^45]: The contact recovery request page is available only to cloud users who are tenant administrators. Source: [Schedule contact recovery requests](https://wfohelp.com/doc/Content/user-guides/application-management/recovery-request.htm), prerequisites list. Checked 2026-10-02. [^46]: Once granular agent states are enabled, existing WFO state grouping configurations no longer align with the new multi-channel agent states, and RTA reporting is interrupted unless state groupings were reconfigured using the new adherence connector. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), entry dated July 22, 2026. Checked 2026-10-02. [^47]: The Username on the Webex CC 2.0 connection should be a service-type account that is never changed, because changing the account can cause duplicate users and teams. Source: [Connection settings for Cisco Webex Contact Center 2.0](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc-2.0.htm), settings list, field 'Username'. Checked 2026-10-02. [^48]: For a single user not recording, the documented checks are user permissions, assignment to a phone, membership of a team configured for recording in a workflow, recording inclusion or exclusion lists, and phone configuration on the telephony side. Source: [Troubleshoot issues with recording](https://wfohelp.com/doc/Content/user-guides/troubleshooting/2024-troubleshooting-project/users-not-recording.htm), section on a single user not recording. Checked 2026-10-02. [^49]: When creating a WFM skill, the time zone is usually set to where the workload is, or to where the resource planners are if the workload covers several time zones. Source: [Create a skill](https://wfohelp.com/doc/Content/user-guides/forecasts/create-skill.htm), field description, Time zone. Checked 2026-10-02. [^50]: Changes to adherence state group settings can take up to 20 minutes to take effect. Source: [Group adherence states](https://wfohelp.com/doc/Content/user-guides/adherence/group-adherence-states.htm), page body, note. Checked 2026-10-02. [^51]: WFM adherence overviews and reports always use state groups, never the individual ACD states. Source: [Group adherence states](https://wfohelp.com/doc/Content/user-guides/adherence/group-adherence-states.htm), page body, paragraph on state groups. Checked 2026-10-02. [^52]: WFM queue and agent statistics and ready-time adherence data are updated periodically during the day, usually every 15 or 30 minutes. Source: [WFM standard reports](https://www.wfohelp.com/doc/Content/user-guides/wfm-reports/about-wfm-reports.htm), data update frequency note. Checked 2026-10-02. [^53]: The Synchronization Interval (Minutes) field on the Webex CC 2.0 connection sets how often users, teams and service queues are synchronized with their Webex Contact Center equivalents. Source: [Connection settings for Cisco Webex Contact Center 2.0](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc-2.0.htm), settings list, field 'Synchronization Interval (Minutes)'. Checked 2026-10-02. [^54]: The WFO connection does not preserve the relationship between Webex CC users and Webex CC teams, so users must be reassigned to teams manually in the WFO platform. Source: [Connection settings for Cisco Webex Contact Center](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc.htm), section 'Teams'. Checked 2026-10-02. [^55]: The WFO connection syncs Webex CC teams of any type, Capacity Based or Agent Based, as long as they are active. Source: [Connection settings for Cisco Webex Contact Center](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc.htm), section 'Teams'. Checked 2026-10-02. [^56]: The Webex Contact Center 2.0 ACD connection has a User Sync setting that enables synchronization of user data into the WFO platform from Webex Contact Center. Source: [Connection settings for Cisco Webex Contact Center 2.0](https://wfohelp.com/doc/Content/user-guides/application-management/acd-config-cisco-webex-cc-2.0.htm), settings list, field 'User Sync'. Checked 2026-10-02. [^57]: The WFO Help Center pages that name Calabrio ONE are the operative documentation for Webex WFO connected to Webex Contact Center, since the same site documents Webex WFO features such as Automated Contact Reconciliation for Webex CC (inferred). Source: [About Automated Contact Reconciliation](https://wfohelp.com/doc/Content/user-guides/application-management/enable-automated-record-reconciliation.htm), page body naming Webex WFO and Webex Contact Center. Checked 2026-10-02. [^58]: Creating a WFM workload requires queue data, either through access to queues via an integration or a queue data file to import. Source: [Create a workload](https://wfohelp.com/doc/Content/user-guides/forecasts/create-workload.htm), prerequisites. Checked 2026-10-02.