# The values the Business Hours activity Status variable can take Canonical: https://warmtransfer.net/knowledge/wxcc-status-variable-values Last verified: 2026-10-14 The Webex Contact Center Flow Designer Business Hours activity exposes an output variable named Status[^45]. Status stores which of the activity's output nodes was chosen during flow execution, and the Flow Designer article describes its values in prose as working hours, holidays, override, or default[^44][^42]. ## How Status is set The Business Hours activity has 4 output nodes: Overrides, Holidays, Working Hours and Default[^21]. The activity uses working hours, holidays and overrides defined in Control Hub to decide which branch the flow takes[^48]. Status records the node that was chosen, so its value depends on which branch rule matched[^44]. | Output node | When the activity takes it | |---|---| | Overrides | The current time is defined as an override in the Overrides list[^32] | | Holidays | The current day is a holiday in the Holidays list[^23] | | Working Hours | The primary node, which evaluates the shift timing of the selected business hour[^51] | | Default | None of the Overrides, Holidays or Working Hours nodes evaluates[^15] | Holiday lists and overrides take precedence over working hours when their timing coincides with the current shift timing[^37]. Within a holiday list or an override, overlapping items are ranked by drag and drop, and higher-ranked items take precedence over lower-ranked ones[^38]. The node labels (Overrides, Holidays, Working Hours, Default) and the prose description of the Status values (working hours, holidays, override, default) are worded differently in the Flow Designer article[^21][^42]. ## Companion output variables The output variable WorkingHoursShift_name stores the name of the shift defined in the working hours[^39]. The output variable Holidays_Name stores the name of the holiday when the current day is a holiday[^22]. The output variable Overrides_Name stores the name of the override that matches the current time[^34]. ## Branching on Status in a flow Flow Designer output variables of activities such as Collect Digits and Menu are referenced with the activity label as a prefix, for example {{CollectDigits.DigitsEntered}}, with the variable name following the label[^26]. A Flow Designer Case activity accepts up to 20 case statements[^3]. If none of the cases are true, the Case activity takes the default case[^2]. Condition activity expressions must be wrapped in double curly braces, and an expression without braces raises a Flow Error[^6]. ## Configuration inputs that affect the result In Schedule Details, the activity offers Static Business Hours, where you pick a Control Hub business hour, and Variable Business Hours, where a variable holds a Business Hour ID[^41]. For Variable Business Hours, the variable must contain the correct Business Hour ID obtained from Control Hub[^49]. If the Variable Business Hours ID is invalid, the flow moves to the error path[^25]. The activity also supports an Undefined Error path for system errors during flow execution[^47]. A Control Hub working hours entity contains 1 or more shifts and a time zone, and it can optionally be linked to a holiday list and an override[^50]. Shifts within a working hours entity cannot overlap one another[^40]. Each Control Hub override has an active or inactive toggle[^31]. An override applies only to working hours in the same time zone, and its time zone cannot be changed after it is selected[^35]. The entry point Timezone setting selects the time zone that business hours use for that entry point[^19]. The channel setup article states that the Business Hours activity takes the appropriate branch based on the business hours configuration associated with it[^18]. Flow Designer custom flow variables can be of a Business Hours kind, which is intended for overriding business hours in an emergency shutdown[^1]. Override flow settings let administrators and supervisors change flow parameters such as business hours without opening the flow[^33]. ## Platform differences: Webex Connect The Webex Connect Business Hours node has a slot output variable rather than Status, and slot takes the values working_hours, holiday, override or no_match[^12]. Slot equals no_match when the current time falls in no configured working hours, holiday list or override[^8]. The node has 4 success edges: inWorkingHours, onHoliday, inOverride and onNoMatch[^13]. Its error edges are onError, onTimeout, onInvalidData, onInvalidChoice and onAuthorizationFail[^7]. The per-slot detail variables (workingHourSlot, holiday and override fields) are populated only when the business is in that slot[^11]. Toggling an override's status in Control Hub does not sync to the Webex Connect Business Hours node, and the documented workaround is to unlink overrides from the business hours[^14]. ## See also - [How a business hours configuration binds to a routing flow](https://warmtransfer.net/knowledge/wxcc-business-hours-flow-binding) - [Time zone scoping of Webex Contact Center business hours](https://warmtransfer.net/knowledge/wxcc-business-hours-time-zones) - [Webex Contact Center business hours overrides and holiday lists](https://warmtransfer.net/knowledge/webex-cc-business-hours-holidays) - [Webex Contact Center holiday and emergency routing overrides](https://warmtransfer.net/knowledge/webex-cc-holiday-emergency-routing) - [Webex Contact Center Flow Designer architecture](https://warmtransfer.net/knowledge/webex-cc-flow-designer) - [Webex Connect Flow Builder node reference](https://warmtransfer.net/knowledge/webex-connect-node-reference) ## Applicability Applies to: Cisco Webex Contact Center and Cisco Webex Connect. Deployments: multi-tenant. Sources checked 2026-10-14. The Flow Designer article documents Business Hours under Activities in Utilities, between BRE Request and Cryptographic Hash[^24]. In Webex Connect, business hours, holidays and overrides created before the feature was implemented do not appear in the Business Hours node[^10]. ## What remains uncertain The exact runtime strings and casing that Status holds are not covered by the sources below. The documentation only gives a prose description of the values and the node labels[^42][^21]. Which time zone wins when the entry point Timezone differs from the working hours time zone is not covered by the sources below. The documentation states only that each carries a time zone setting[^19][^50]. Which Status results when an override and a holiday match the same moment is not covered by the sources below. The documented precedence covers only holiday lists and overrides over working hours, and ranking within a single holiday list or override[^37][^38]. Whether an inactive override can still produce the Override node in Flow Designer is not covered by the sources below. The documented toggle sync limitation applies to the Webex Connect node[^14]. Whether Case and Condition comparisons against Status are case sensitive is not covered by the sources below. The value left in Status after an invalid ID or an Undefined Error exit is not covered by the sources below. The content of the Webex Contact Center Business Hours API page is not covered by the sources below. The content of the business hours usage flow template article is not covered by the sources below. ## Sources [^1]: Flow Designer custom flow variables can be of a Business Hours kind, intended to override business hours in an emergency shutdown. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Custom variables > Create Custom Flow Variables (variable type list). Checked 2026-10-14. [^2]: In the Flow Designer Case activity, if none of the cases are true the default case is taken. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Case activity. Checked 2026-10-14. [^3]: A Flow Designer Case activity accepts up to 20 case statements. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Case activity > Case setting. Checked 2026-10-14. [^4]: The Flow Designer article does not state whether Case or Condition comparisons are case-sensitive, so a Status comparison's tolerance of casing differences is undocumented (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Case activity and Condition activity. Checked 2026-10-14. [^5]: The Control Hub business hours article does not describe the Business Hours activity's branches or its Status variable and defers flow usage to the Flow Designer article. Source: [Set up business hours for Webex Contact Center](https://help.webex.com/en-us/article/dqekw4/Set-up-business-hours-for-Webex-Contact-Center), Whole article; closing reference to the Flow Designer article. Checked 2026-10-14. [^6]: Flow Designer Condition activity expressions must be wrapped in double curly braces, and an expression without braces raises a Flow Error. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Condition activity. Checked 2026-10-14. [^7]: The Webex Connect Business Hours node has error edges onError, onTimeout, onInvalidData, onInvalidChoice and onAuthorizationFail. Source: [Business Hours - WXCC](https://help.webexconnect.io/docs/wxcc-engage-business-hours), Node edges > Errors. Checked 2026-10-14. [^8]: In Webex Connect, slot equals no_match when the current time falls in no configured working hours, holiday list or override. Source: [Business Hours - WXCC](https://help.webexconnect.io/docs/wxcc-engage-business-hours), Output variables table > slot row (no_match explanation). Checked 2026-10-14. [^9]: The Webex Connect slot literals (working_hours, holiday, override, no_match) belong to a different node and must not be assumed to be the runtime strings of the Flow Designer Status variable (inferred). Source: [Business Hours - WXCC](https://help.webexconnect.io/docs/wxcc-engage-business-hours), Output variables table > slot row; compare Flow Designer article Business Hours > Output variables. Checked 2026-10-14. [^10]: In Webex Connect, business hours, holidays and overrides created before the feature was implemented do not appear in the Business Hours node. Source: [Business Hours - WXCC](https://help.webexconnect.io/docs/wxcc-engage-business-hours), Limitations section. Checked 2026-10-14. [^11]: In Webex Connect the per-slot detail variables (workingHourSlot, holiday, override fields) are populated only when the business is in that slot. Source: [Business Hours - WXCC](https://help.webexconnect.io/docs/wxcc-engage-business-hours), Output variables table > workingHourSlot.*, holiday.*, override.* rows. Checked 2026-10-14. [^12]: The Webex Connect Business Hours node's slot output variable takes the values working_hours, holiday, override or no_match. Source: [Business Hours - WXCC](https://help.webexconnect.io/docs/wxcc-engage-business-hours), Output variables table > slot row. Checked 2026-10-14. [^13]: The Webex Connect Business Hours node has four success edges: inWorkingHours, onHoliday, inOverride and onNoMatch. Source: [Business Hours - WXCC](https://help.webexconnect.io/docs/wxcc-engage-business-hours), Node edges > Success. Checked 2026-10-14. [^14]: In Webex Connect, toggling an override's status in Control Hub does not sync to the Business Hours node, and the documented workaround is to unlink overrides from the business hours. Source: [Business Hours - WXCC](https://help.webexconnect.io/docs/wxcc-engage-business-hours), Limitations section. Checked 2026-10-14. [^15]: The Business Hours activity takes the Default branch when none of the Overrides, Holidays or Working Hours nodes evaluates. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > business hours nodes list item 4 (Default). Checked 2026-10-14. [^16]: Flow Designer's Default outcome and Webex Connect's no_match outcome cover the same situation (no working hours, holiday or override match) under different names (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Utilities > Business Hours > business hours nodes list item 4; compare webexconnect-docs-wxcc-engage-business-hours Output variables > slot row. Checked 2026-10-14. [^17]: Flow Designer raises a flow validation error if any of the Business Hours activity's ordered list inputs is empty. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours (validation note). Checked 2026-10-14. [^18]: The channel setup article states that the Business Hours activity takes the appropriate branch based on the business hours configuration associated with it. Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), Create a channel > step 5 > Entry Point Settings table > Routing Flow row. Checked 2026-10-14. [^19]: The entry point Timezone setting selects the time zone that business hours use for that entry point. Source: [Set up a channel](https://help.webex.com/en-us/article/ewuay1/Set-up-a-channel), Create a channel > step 5 > Entry Point Settings table > Timezone row. Checked 2026-10-14. [^20]: When the activity exits by the error path rather than one of its four nodes, the value left in Status is undocumented, so flows should not branch on Status after an error exit (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > Variable Business Hours and Output variables. Checked 2026-10-14. [^21]: The Business Hours activity has four output nodes: Overrides, Holidays, Working Hours and Default. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > business hours nodes list (items 1-4). Checked 2026-10-14. [^22]: The Business Hours activity output variable Holidays_Name stores the name of the holiday when the current day is a holiday. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > Output variables > Holidays_Name row. Checked 2026-10-14. [^23]: The Business Hours activity takes the Holidays branch when the current day is a holiday in the Holidays list. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > business hours nodes list item 2 (Holidays). Checked 2026-10-14. [^24]: Business Hours is documented under Activities in Utilities in the Flow Designer article, between BRE Request and Cryptographic Hash. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities (activity list). Checked 2026-10-14. [^25]: If the Variable Business Hours ID is invalid, the flow moves to the error path. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > configuration step 3 > Variable Business Hours. Checked 2026-10-14. [^26]: Flow Designer output variables of activities such as Collect Digits and Menu are referenced with the activity label as a prefix, for example {{CollectDigits.DigitsEntered}}, and the name follows the label. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Collect Digits (output variable paragraph) and Menu (output variable paragraph). Checked 2026-10-14. [^27]: The name variables are documented only for the case where their node matches, so their content when another node is chosen (for example Holidays_Name on a Working Hours outcome) is undocumented (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > Output variables. Checked 2026-10-14. [^28]: The Flow Designer article does not state a data type for the Business Hours activity's Status output variable. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > Output variables. Checked 2026-10-14. [^29]: The Flow Designer article does not publish the literal string values (exact spelling, casing or separators) that the Status variable holds at runtime. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours (whole section). Checked 2026-10-14. [^30]: The article names the node Overrides but the Override branch and the Status prose use the singular override, so the documentation itself is inconsistent about the spelling a Status comparison should use (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > business hours nodes list item 1 and Output variables > Status row. Checked 2026-10-14. [^31]: Each Control Hub override has an active or inactive toggle. Source: [Set up business hours for Webex Contact Center](https://help.webex.com/en-us/article/dqekw4/Set-up-business-hours-for-Webex-Contact-Center), Manage overrides > Create an override. Checked 2026-10-14. [^32]: The Business Hours activity takes the Override branch when the current time is defined as an override in the Overrides list. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > business hours nodes list item 1 (Overrides). Checked 2026-10-14. [^33]: Override flow settings let administrators and supervisors change flow parameters such as business hours without opening the flow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Override flow settings (introductory paragraph). Checked 2026-10-14. [^34]: The Business Hours activity output variable Overrides_Name stores the name of the override that matches the current time. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > Output variables > Overrides_Name row. Checked 2026-10-14. [^35]: An override applies only to working hours in the same time zone, and its time zone cannot be changed after it is selected. Source: [Set up business hours for Webex Contact Center](https://help.webex.com/en-us/article/dqekw4/Set-up-business-hours-for-Webex-Contact-Center), Manage overrides > Create an override (time zone setting). Checked 2026-10-14. [^36]: Because the article only states that holidays and overrides each beat working hours, which Status value results when an override and a holiday both match the same moment is not determinable from the documentation (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > business hours nodes list and precedence note. Checked 2026-10-14. [^37]: Holiday lists and overrides take precedence over working hours when their timing coincides with the current shift timing. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > note following the business hours nodes list. Checked 2026-10-14. [^38]: Within a holiday list or an override, overlapping items are ranked by drag and drop and higher-ranked items take precedence over lower-ranked ones. Source: [Set up business hours for Webex Contact Center](https://help.webex.com/en-us/article/dqekw4/Set-up-business-hours-for-Webex-Contact-Center), Manage holiday lists > Create a holiday list; Manage overrides > Create an override (ranking examples). Checked 2026-10-14. [^39]: The Business Hours activity output variable WorkingHoursShift_name stores the name of the shift defined in the working hours. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > Output variables > WorkingHoursShift_name row. Checked 2026-10-14. [^40]: Shifts within a Control Hub working hours entity cannot overlap one another. Source: [Set up business hours for Webex Contact Center](https://help.webex.com/en-us/article/dqekw4/Set-up-business-hours-for-Webex-Contact-Center), Manage working hours > Create working hours (shift settings). Checked 2026-10-14. [^41]: In Schedule Details the Business Hours activity offers Static Business Hours (pick a Control Hub business hour) and Variable Business Hours (a variable holding a Business Hour ID). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > configuration step 3 (Schedule Details). Checked 2026-10-14. [^42]: The Flow Designer article describes the Status values in prose as working hours, holidays, override, or default. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > Output variables > Status row. Checked 2026-10-14. [^43]: By analogy with other activities, Status is probably referenced as {{.Status}}, but the Business Hours section does not show this syntax (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Activities in Contact Handling > Collect Digits and Menu; Activities in Utilities > Business Hours > Output variables. Checked 2026-10-14. [^44]: The Status output variable stores which of the activity's output nodes was chosen during flow execution. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > Output variables > Status row. Checked 2026-10-14. [^45]: The Webex Contact Center Flow Designer Business Hours activity exposes an output variable named Status. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > Output variables. Checked 2026-10-14. [^46]: The Business Hours flow template Help Center article presents its example flow only as a linked PDF and its HTML body names no Status variable or branch logic. Source: [Business Hours](https://help.webex.com/en-us/article/nvk1s2j/Business-Hours), Article body (single paragraph and PDF attachment). Checked 2026-10-14. [^47]: The Business Hours activity supports an Undefined Error path for system errors during flow execution. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > error handling note. Checked 2026-10-14. [^48]: The Business Hours activity uses working hours, holidays and overrides defined in Control Hub to decide which branch the flow takes. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours (introductory paragraphs). Checked 2026-10-14. [^49]: For Variable Business Hours the variable must contain the correct Business Hour ID obtained from Control Hub. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > configuration step 3 > Variable Business Hours. Checked 2026-10-14. [^50]: A Control Hub working hours entity contains one or more shifts and a time zone and can optionally be linked to a holiday list and an override. Source: [Set up business hours for Webex Contact Center](https://help.webex.com/en-us/article/dqekw4/Set-up-business-hours-for-Webex-Contact-Center), Manage working hours > Create working hours. Checked 2026-10-14. [^51]: Working Hours is the primary node of the Business Hours activity and evaluates the shift timing of the selected business hour. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Business Hours > business hours nodes list item 3 (Working Hours). Checked 2026-10-14.