Mastering Solution Health Hub: Troubleshooting Tips for Dynamics 365 Customer Service

Table of Contents

The Dynamics 365 Customer Service Solution Health Hub is a powerful tool designed to proactively identify and help resolve potential issues within your Customer Service environment. By regularly utilizing this hub, administrators and system customizers can ensure the smooth operation of their Dynamics 365 Customer Service instance, minimizing disruptions and optimizing performance. This article delves into common troubleshooting tips derived from the Solution Health Hub checks, providing guidance on understanding and resolving identified issues.

Automatic Record Creation Process Definitions in Draft Status¶

One crucial aspect of Dynamics 365 Customer Service is the automation of record creation. This is often achieved through Automatic Record Creation (ARC) rules, which streamline the process of converting incoming activities like emails or social media posts into records such as cases or leads. The Solution Health Hub diligently checks the status of process definitions related to these ARC rules. Specifically, it identifies if any processes are in a draft state when they should be active for the automatic record creation to function correctly.

The system verifies whether the custom actions ExecutePrimaryCreatePostActions and ExecuteARC, which are integral to the ARC process, are in the active state when an ARC rule is in use. When processes associated with automatic record creation are found in a deactivated or draft state, it signifies a potential problem. These processes are often deactivated automatically by the system under certain conditions or might have been left in draft after configuration.

If these deactivated processes are essential for your business logic, they need to be reactivated. To resolve this, navigate to the specific ARC rule identified by the Solution Health Hub. Within the rule settings, you should find an option to Resolve the issue. Selecting this option typically reactivates the necessary processes, ensuring your automatic record creation rules function as intended. It is vital to review deactivated processes to determine if they are indeed required for your operational workflows before reactivating them.

Check if Activity Monitor for Automatic Record Creation is Enabled¶

Monitoring the effectiveness of your automatic record creation rules is paramount for maintaining a healthy and efficient Customer Service system. The Activity monitor is a valuable feature that allows you to track the success and failure of these rules. The Solution Health Hub includes a check to ensure that the activity monitor is enabled for automatic record creation.

This check specifically looks at the flag values for msdyn_ArcActivityMonitorForFailedScenarios and msdyn_ArcActivityMonitorForSkippedScenarios. These flags determine whether the activity monitor is actively tracking failed and skipped scenarios related to ARC rules. If the activity monitor is not enabled, you lose visibility into the performance and potential issues within your automated record creation processes.

When the Solution Health Hub flags that the activity monitor is not enabled, it’s crucial to enable it. Activating the activity monitor provides valuable insights into rule execution, allowing you to identify rules that might be failing or being skipped. This proactive monitoring empowers you to address issues promptly, ensuring that all incoming interactions are correctly processed and converted into relevant records. Enabling the activity monitor is a best practice for maintaining the reliability and efficiency of your automatic record creation setup. Refer to the documentation on “Use activity monitor to review and track rules” for detailed steps on enabling and utilizing this feature.

Check if autoRouteToOwnerQueue for the Email entity is enabled¶

Email is a primary channel for customer interaction in many organizations using Dynamics 365 Customer Service. Efficient routing of emails to the appropriate users or queues is essential for timely and effective customer service. The autoRouteToOwnerQueue setting for the Email entity plays a significant role in this routing process. The Solution Health Hub includes a check to ensure this setting is configured correctly in conjunction with automatic record creation rules.

This check evaluates whether automatic record creation rules are enabled and if the autoRouteToOwnerQueue option is set for the Email entity. If the “Automatically move records to owner’s default queue” checkbox is selected for the Email entity, it can interfere with the intended routing logic of your automatic record creation rules. In such cases, the rule for creating records automatically might not trigger correctly for the desired user, leading to misrouted emails and potentially delayed customer service.

When the Solution Health Hub identifies this configuration issue, it indicates a potential conflict in your email routing setup. To ensure emails are correctly routed according to your ARC rules, review the autoRouteToOwnerQueue setting for the Email entity. Carefully consider if automatically moving emails to the owner’s default queue aligns with your intended routing strategy, especially when using automatic record creation. For more detailed information on entity record routing, consult the documentation on “Entity records routing.” Adjusting this setting might be necessary to ensure proper email handling and assignment within your Dynamics 365 Customer Service environment.

Check if Customer Service forms are from unmanaged layer¶

Forms are the primary interface through which users interact with data within Dynamics 365 Customer Service. Maintaining the integrity and intended behavior of these forms is crucial for user experience and data consistency. The Solution Health Hub includes a check to verify the layer from which Customer Service forms are being served. Specifically, it checks if these forms are originating from an unmanaged layer.

The check is triggered when Customer Service forms are found in the unmanaged layer. This is considered a potential issue because unmanaged solutions can overwrite critical Customer Service metadata fixes and updates. In a production environment, it is strongly recommended to avoid placing system forms in active, unmanaged layers. Unmanaged customizations are intended for development and testing environments, where flexibility and rapid changes are prioritized.

If the Solution Health Hub flags this issue, it indicates that your Customer Service forms are susceptible to being overridden by unmanaged customizations. To resolve this, you should investigate the unmanaged layers within your Dynamics 365 environment and identify any customizations applied to Customer Service forms. Ideally, system forms should reside in managed layers in a production environment to ensure stability and adherence to best practices. Consider moving customizations from unmanaged layers to managed solutions or applying customizations in a non-destructive manner to maintain the intended behavior of Customer Service forms.

Check workflow type for convert rule and convert rule items¶

Convert rules, also known as automatic record creation rules, rely on workflows to automate the process of converting activities into records. The type and state of these workflows are critical for the proper functioning of the convert rules. The Solution Health Hub performs a comprehensive check on the workflow types associated with convert rules and their items, ensuring they align with the rule’s configuration and intended behavior.

This check distinguishes between Modern rules and Legacy rules.

• Modern Rule: For rules created in the Unified Interface, the associated workflow should be a Power Automate flow. Power Automate flows are the modern, cloud-based workflow engine for Dynamics 365.
• Legacy Rule: For rules created in the classic interface, the associated workflow should be a legacy workflow (Dynamics 365 workflow). Legacy workflows are the older, on-premises workflow engine.

Additionally, the check verifies the Workflow state based on the rule’s activation status:

• Active Rule: For an active convert rule, the associated workflow on both the rule and its rule items should be present and in an active state. Active workflows are necessary for the rule to function.
• Draft Rule: For a convert rule in draft status, it should ideally have no associated workflow at the rule level. However, rule items within a draft rule might have associated workflows, which should be in a draft state themselves.

The Solution Health Hub identifies several potential Workflow type issues and Workflow state issues:

• Workflow type issue (Unified Interface/Legacy mismatch): This occurs when you perform an activate or deactivate action on a legacy rule within the Unified Interface form. This can lead to inconsistencies in workflow associations.
• Workflow type issue (Modern rule items in legacy experience): This occurs when rule items for a modern rule are created in the legacy (classic) experience. Again, this can cause mismatches in workflow types.
• Workflow state issue (Power Automate flow status): Manually turning on or off flows in Power Automate that are associated with convert rules can lead to workflow state issues and disrupt the rule’s operation.

How to fix the issue:

• Workflow state issue: The system should automatically correct workflow state issues, updating the relevant workflow to its required state. However, manual intervention might be necessary in some cases.
• Workflow type issue: Workflow type issues typically require contacting Microsoft Support for resolution due to the complexity of underlying configuration mismatches.

Recommendations:

• Rules created in the Unified Interface should only be edited, activated, or deactivated within the Unified Interface experience.
• Rules created in the legacy experience should only be managed within the legacy experience.
• Avoid manually turning on or off flows in Power Automate that are associated with automatic record creation rules. Let the system manage the flow state through the convert rule management interface.

ConditionXml format check¶

Convert rules often utilize conditions to define when a rule should be triggered and applied. These conditions are represented using XML formats, either conditionxml for legacy rules or FetchXML for modern rules. Maintaining the correct format for these conditions is vital for the accurate execution of convert rules. The Solution Health Hub performs a check to ensure the conditionxml format is consistent with the rule type.

This check distinguishes between Modern rules and Legacy rules in terms of the expected conditionxml format:

• Modern rule: For rules created in the Unified Interface, the conditionxml attribute value of all related rule items should be in FetchXML format. FetchXML is the modern query language for Dynamics 365.
• Legacy rule: For rules created in the classic interface, the conditionxml attribute value of all related rule items should be in conditionxml format. ConditionXML is the older, legacy format.

The Solution Health Hub flags issues when the format is mismatched for the rule type, indicating a potential configuration problem. Common causes for format mismatches include:

• Format mismatch in rule type: The condition XML format used does not align with whether the rule is a modern or legacy rule.
• Unified Interface/Legacy action mismatch: Performing activate or deactivate actions on a legacy rule in the Unified Interface form experience can lead to format inconsistencies.
• Modern rule items in legacy experience: Creating rule items for a modern rule in the legacy experience can also result in incorrect condition XML formats.

Recommendation:

To avoid conditionxml format issues, adhere to the following best practice:

• Rules created in the Unified Interface app and legacy app should be edited, activated, or deactivated in the corresponding app, respectively. Do not use the apps interchangeably for managing convert rules. Maintaining consistency in the interface used for rule management helps prevent format mismatches and ensures the rules function as expected.

Custom customizations on the Customer Service Hub site map¶

The site map in Dynamics 365 Customer Service Hub provides the navigation structure for users. Customizing the site map offers flexibility, but it can also introduce complexities when updates and managed solutions are applied. The Solution Health Hub includes a check to detect customizations on the Customer Service Hub site map.

This check specifically looks for any modifications made to the default Customer Service Hub site map. The check fails when the site map is customized. While customizations can be beneficial, they can sometimes conflict with updates and managed solutions, particularly concerning navigation merges. Unmanaged customizations to the site map can be overwritten or cause unexpected behavior when managed solutions, including Customer Service updates, are deployed.

If the Solution Health Hub identifies customizations on the Customer Service Hub site map, it’s advisable to review these customizations. Consider whether the customizations are essential and if they can be achieved through more manageable approaches, such as using application ribbons or other extension points. For more information on managing site map customizations and merge behavior, refer to the documentation on “Merge site map customizations”. In production environments, minimizing direct customizations to system site maps is often recommended to ensure smoother updates and maintainability.

Custom customizations on the Customer Service Workspace site map¶

Similar to the Customer Service Hub, the Customer Service Workspace also relies on a site map to define its navigation. Customizing the Customer Service Workspace site map carries similar considerations regarding maintainability and potential conflicts with updates. The Solution Health Hub includes a dedicated check for customizations on the Customer Service Workspace site map.

This check mirrors the Customer Service Hub site map check and fails when the site map is customized. Customizations, while offering tailored navigation, can complicate the process of applying updates and managed solutions to the Customer Service Workspace. Unmanaged site map customizations can be particularly problematic as they can be overwritten or lead to unpredictable navigation behavior after updates.

When the Solution Health Hub flags customizations on the Customer Service Workspace site map, it’s recommended to assess the necessity of these customizations. Explore alternative methods for achieving desired navigation changes, such as using application ribbons or configuration settings, rather than directly modifying the system site map. Consult the documentation on “Merge site map customizations” for a deeper understanding of site map merging and customization best practices. In production environments, aim to minimize direct customizations to system site maps for improved update management and system stability.

Customized option sets¶

Option sets (picklists or dropdowns) are fundamental components for data entry and selection in Dynamics 365 Customer Service. While customization is a core feature of Dynamics 365, customizing system option sets, especially in Customer Service, can sometimes lead to unintended consequences. The Solution Health Hub includes a check to detect customizations applied to option sets within Customer Service.

This check identifies whether any option set within the Customer Service area has been customized. The check flags an issue when an option set has been modified by customization. Customizing system option sets can introduce unexpected behavior, particularly when these option sets are used across multiple entities and processes within Customer Service. Customizations to one option set might inadvertently impact other areas relying on the same option set, potentially causing data inconsistencies or functional issues.

If the Solution Health Hub detects customized option sets, it’s crucial to carefully evaluate these customizations. Determine if the customizations are truly necessary for your business requirements. If the customizations are not essential, it’s recommended to manually remove customizations from the Customer Service option set. Consider alternative approaches to achieve your desired functionality that do not involve directly modifying system option sets, such as creating custom option sets or using business rules for conditional logic. Prioritizing minimal customization of system option sets helps maintain the stability and predictability of your Dynamics 365 Customer Service environment.

Deleted Sdk message processing steps¶

SDK message processing steps (also known as plug-in steps) are a core part of the Dynamics 365 platform, enabling custom code execution in response to system events. Customer Service relies on specific SDK message processing steps for its intended functionality. Deleting these steps can severely disrupt Customer Service operations. The Solution Health Hub includes a critical check to detect deleted SDK message processing steps.

This check verifies whether any of the shipped Customer Service SDK message processing steps have been deleted from the system. The check fails if any such steps are deleted. Deleting these system-provided steps can lead to incorrect and unpredictable behavior when using Customer Service. These steps are integral to the internal workings of Customer Service features, and their absence can break core functionalities.

If the Solution Health Hub identifies deleted SDK message processing steps, it signifies a serious issue requiring immediate attention. Contact Microsoft Support to resolve the issue. Restoring deleted system SDK message processing steps typically requires administrative intervention and might necessitate assistance from Microsoft to ensure proper re-establishment of the required steps and functionalities. Preventing accidental or intentional deletion of system SDK message processing steps is crucial for maintaining the integrity of your Dynamics 365 Customer Service environment.

Disabled Sdk message processing steps¶

Similar to deleted SDK message processing steps, disabled SDK message processing steps can also disrupt the intended behavior of Dynamics 365 Customer Service. While disabling steps is less severe than deleting them, it can still lead to functional issues. The Solution Health Hub includes a check to identify disabled SDK message processing steps.

This check verifies whether any SDK message processing steps within Customer Service are disabled. The check flags an issue when SdkMessageProcessingSteps are deactivated. Disabled SDK message processing steps will lead to incorrect behavior when using Customer Service. Like deleted steps, these steps are essential for the proper execution of Customer Service features, and disabling them can break or degrade functionality.

If the Solution Health Hub detects disabled SDK message processing steps, it’s important to review if the disabled SdkMessageProcessingSteps processes are required for your business logic and reactivate them if necessary. In many cases, system SDK message processing steps should be active for Customer Service to operate correctly. To resolve the issue, navigate to the identified disabled SDK message processing steps within customizations and reactivate them. However, before reactivating, carefully consider if there was a specific reason for disabling them and if reactivation aligns with your intended system configuration. Generally, system-provided SDK message processing steps for Customer Service should remain active in production environments.

Process definitions in draft status¶

Processes (workflows, dialogs, business process flows) are fundamental to automating business logic within Dynamics 365 Customer Service. For processes to execute and automate tasks, they must be in an active state. Processes in draft status are not operational. The Solution Health Hub checks for process definitions related to Customer Service that are in a draft status.

This check examines process definitions and identifies if any are in a draft state. Note: The validation check specifically excludes ManageContract, Contractline, and Entitlement workflows when they are in the draft state, likely due to their less critical nature or different operational context. However, for other Customer Service-related processes, being in draft is generally problematic.

The Solution Health Hub flags an issue when processes are deactivated. Customer Service might not work correctly when processes are disabled. Deactivated or draft processes cannot execute their intended automated steps, potentially leading to gaps in automation, missed notifications, or incorrect data updates.

To resolve this issue, reactivate process definitions from customizations. Navigate to the identified process definitions within the customization area of Dynamics 365 and change their status from draft to active. Before activating, review the process to ensure it aligns with your current business requirements and intended automation logic. Activating essential processes is crucial for maintaining the automated workflows within your Dynamics 365 Customer Service environment.

Process definitions owned by disabled users¶

Processes in Dynamics 365 are often associated with an owner user account. If a process is owned by a disabled user, it can lead to execution failures because the system might not be able to run the process under the context of a disabled user. The Solution Health Hub checks for process definitions in the system that are assigned to disabled users.

This check examines process ownership and identifies processes where the owner user account is disabled. Processes will fail because they are owned by disabled users. When a process attempts to run under the security context of a disabled user, it may encounter permission issues or fail to execute entirely. This can disrupt automated workflows and lead to operational problems.

The Solution Health Hub highlights the importance of ensuring that all workflows are assigned to users who have the required permissions. To resolve this issue, you have two primary options:

1. Reactivate the user accounts that own workflows: If the user accounts were disabled in error or if there is a reason to reactivate them, this can resolve the process ownership issue. However, consider the implications of reactivating user accounts, especially if they were disabled for security or access control reasons.
2. Assign the workflows to another user account with the proper security privileges: A more common and often preferred solution is to reassign the ownership of the affected workflows to an active user account that has the necessary security privileges to run the processes. This ensures that the processes can execute successfully without relying on disabled user accounts.

Choose the resolution approach that best aligns with your user management policies and security requirements. Ensuring processes are owned by active and properly permissioned users is crucial for maintaining the reliability of automated workflows in Dynamics 365 Customer Service.

Validate Email response template type for Modern Automatic Record Creation¶

Automatic Record Creation (ARC) rules can be configured to send automatic email responses to customers when activities are processed. These email responses rely on email templates. For modern ARC rules, it’s essential that the template type of the auto-response email template matches the primary entity set on the rule items. The Solution Health Hub validates this template type consistency.

This check focuses on modern ARC rules and examines the relationship between the email template and the rule items. It looks at three key attributes:

• responsetemplateid: Stores the auto-response email template on the convertrule entity (the ARC rule itself).
• templatetypecode: Stores the template type code on the email template entity. This defines the entity type the template is designed for (e.g., Case, Lead).
• primarycreateentitylogicalname: Stores the primary create entity on the convertruleitem entity (items within the ARC rule). This specifies the entity type that will be created by the rule item.

The check identifies an issue when the template type code of the auto-response email template set on a rule didn’t match with the primary entity set on its rule items. In such cases, the automatic response won’t be sent because the template type didn’t match the rule item primary action entity type. While this mismatch prevents the automatic response from being sent, it won’t cause a rule failure in terms of record creation. The rule will still create the record, but the auto-response email will not be triggered.

If the Solution Health Hub flags this issue, it indicates a configuration inconsistency in your ARC rule setup. To resolve this, ensure that the email template selected for auto-response is of the correct template type, which aligns with the primary entity type being created by the rule items. For example, if your rule items are creating Case records, the auto-response email template should be of the “Case” template type. Correcting this template type mismatch ensures that automatic email responses are sent as intended when ARC rules are triggered.

Waiting workflow instances are owned by disabled users¶

Workflow instances in Dynamics 365 can sometimes enter a “waiting” state, often due to delays or pauses within the workflow logic. Similar to process definitions owned by disabled users, waiting workflow instances owned by disabled users can also lead to failures. The Solution Health Hub detects waiting workflow instances that are assigned to disabled users.

This check specifically identifies workflow instances that are currently in a waiting state and are owned by user accounts that are disabled. These workflows will fail to correctly generate the records that they are supposed to generate. When a waiting workflow instance attempts to resume execution under the context of a disabled user, it may encounter permission errors or fail to proceed, preventing the workflow from completing its intended tasks, such as record creation or updates.

The Solution Health Hub highlights that the workflows are assigned to disabled users. To resolve this issue, similar to process definitions owned by disabled users, you have two primary options:

1. Reactivate the user accounts that own the workflows: If reactivating the user accounts is feasible and aligned with your user management policies, this can resolve the ownership issue for the waiting workflow instances.
2. Assign the workflows to another user account with the proper security privileges: Reassigning the ownership of the waiting workflow instances to an active user account with appropriate security privileges is often the more practical solution. This allows the workflows to resume execution and complete their intended tasks without being blocked by the disabled user context.

Choose the resolution approach that best fits your user management strategy and security considerations. Ensuring that waiting workflow instances are owned by active and properly permissioned users is vital for the reliable execution of workflows and the automated processes they drive in Dynamics 365 Customer Service.

Agents should have capacity¶

Capacity management is a crucial aspect of efficient workload distribution in Dynamics 365 Customer Service, particularly when using Omnichannel features. Agents, who handle customer interactions, need to have capacity defined to ensure workload is distributed fairly and effectively. The Solution Health Hub verifies that capacity has been defined for agents.

This check ensures that agents are properly configured with capacity settings. Agents should have capacity defined to participate in workload distribution and routing within Omnichannel for Customer Service. Capacity represents the amount of work an agent can handle concurrently. Without defined capacity, the system cannot effectively route work items to agents, potentially leading to inefficient resource utilization and delays in customer service.

If the Solution Health Hub flags this issue, it indicates that some agents may not have capacity defined. To resolve this, navigate to the user settings for the identified agents and configure their capacity. Capacity is typically defined within user profiles or Omnichannel user settings. Ensure that agents have appropriate capacity values assigned based on their roles, skills, and workload expectations. Refer to the documentation on “Manage users” for detailed guidance on configuring user capacity. Properly defining agent capacity is essential for effective workload management and optimal agent utilization in Dynamics 365 Customer Service.

Bots should have capacity¶

Bots, when integrated into Dynamics 365 Customer Service, act as virtual agents and also require capacity configuration. Similar to human agents, bots need capacity defined to manage their workload and participate in routing. The Solution Health Hub verifies that bots have capacity defined and that it is greater than zero.

This check ensures that bots are configured with a capacity value that is greater than zero. Verifies that the bot’s capacity is greater than zero. Bots, even though they are automated, still consume resources and need to be factored into workload distribution. A bot with zero capacity will not be considered for work item routing, effectively rendering it unusable within Omnichannel for Customer Service.

If the Solution Health Hub flags this issue, it indicates that one or more bots have a capacity of zero or no capacity defined. To resolve this, configure the capacity for the identified bots to a value greater than zero. Bot capacity is typically configured during bot setup or within Omnichannel administration settings. Ensure that bots have appropriate capacity values assigned to enable them to participate in workload routing and handle customer interactions. Consult the documentation on “Configure a bot” for detailed steps on bot configuration, including capacity settings. Setting bot capacity to a positive value is crucial for enabling bots to effectively contribute to customer service operations.

Bots shouldn’t have potentially low capacity¶

While bots need to have capacity defined, they also need to have sufficient capacity relative to the work streams they are assigned to. Bots are typically designed to handle a high volume of interactions, and their capacity should reflect this. The Solution Health Hub includes a check to ensure that bots don’t have potentially low capacity compared to work streams.

This check specifically verifies that the bot’s capacity is at least a hundred times the capacity of the work stream. This ratio is a guideline to ensure that bots have significantly higher capacity than the work streams they are associated with. Work streams define the flow of work items, and if a bot’s capacity is too low relative to the work stream capacity, it might become a bottleneck in handling interactions within that work stream.

If the Solution Health Hub flags this issue, it suggests that the capacity configured for a bot might be too low and could potentially limit its effectiveness. To resolve this, review the capacity settings for the identified bot and the work stream it is associated with. Increase the bot’s capacity to be at least a hundred times greater than the work stream capacity. This adjustment ensures that the bot has sufficient capacity to handle the expected volume of interactions within the work stream and prevents it from becoming a limiting factor in workload processing. Optimizing bot capacity relative to work stream capacity is crucial for maximizing the efficiency and scalability of bot-driven customer service operations.

Custom channel configuration should have work stream¶

Custom channels in Dynamics 365 Customer Service allow organizations to integrate with channels beyond the standard offerings, such as custom messaging platforms or communication interfaces. For custom channels to function within Omnichannel, they must be associated with an active work stream. The Solution Health Hub verifies that all custom channels have an active work stream configured.

This check ensures that each custom channel configuration is linked to an active work stream. Verifies that all custom channels have an active work stream. Work streams define the routing and processing logic for incoming interactions. Without an active work stream, a custom channel cannot properly route and manage customer interactions within Omnichannel. The custom channel will essentially be disconnected from the Omnichannel routing engine.

If the Solution Health Hub flags this issue, it indicates that one or more custom channel configurations are missing an active work stream association. To resolve this, navigate to the custom channel configuration settings and associate it with an active work stream. If a suitable work stream does not exist, you may need to create a new work stream specifically for the custom channel. Ensure that the selected work stream is active and properly configured to handle the types of interactions expected from the custom channel. Refer to the documentation on “Configure a custom channel” for guidance on setting up custom channels and work stream associations. Linking custom channels to active work streams is essential for enabling them to function correctly within the Omnichannel framework.

Custom channel settings should have all required fields¶

Custom channels in Dynamics 365 Customer Service require specific configuration settings to be properly defined. Missing required fields in the custom channel settings can prevent the channel from functioning correctly. The Solution Health Hub verifies that custom channel settings have all the necessary fields populated, specifically checking for the messaging endpoint URL field.

This check focuses on the configuration details of custom channels and verifies that custom channel settings have the messaging endpoint URL field. The messaging endpoint URL is a critical piece of information that tells Dynamics 365 how to communicate with the custom channel’s underlying messaging platform or interface. Without a valid messaging endpoint URL, Dynamics 365 cannot send or receive messages through the custom channel.

If the Solution Health Hub flags this issue, it indicates that the messaging endpoint URL field is missing or empty in the settings for one or more custom channels. To resolve this, edit the settings for the identified custom channel and ensure that the messaging endpoint URL field is populated with the correct URL for your custom channel’s messaging endpoint. Obtain the correct messaging endpoint URL from your custom channel provider or system administrator. Verifying and populating all required fields, especially the messaging endpoint URL, is crucial for ensuring that custom channels can establish communication and function correctly within Dynamics 365 Customer Service.

Facebook page configuration should have work stream¶

Facebook is a popular channel for customer interaction, and Dynamics 365 Customer Service offers integration with Facebook pages through Omnichannel. For Facebook pages to be effectively managed within Omnichannel, they need to be associated with an active work stream. The Solution Health Hub verifies that all configured Facebook pages have an active work stream.

This check ensures that each Facebook page configured for Omnichannel integration is linked to an active work stream. Verifies that all Facebook pages have an active work stream. Similar to custom channels, work streams define the routing and processing logic for interactions coming from Facebook pages. Without an active work stream, Facebook messages cannot be properly routed and handled within Omnichannel. The Facebook page integration will be ineffective.

If the Solution Health Hub flags this issue, it indicates that one or more Facebook page configurations are missing an active work stream association. To resolve this, navigate to the Facebook page configuration settings in Omnichannel and associate each page with an active work stream. If a suitable work stream does not exist, you might need to create a new work stream specifically for Facebook interactions. Ensure that the selected work stream is active and configured to handle Facebook messages appropriately. Refer to the documentation on “Configure a Facebook channel” for guidance on setting up Facebook channels and work stream associations. Linking Facebook pages to active work streams is essential for enabling effective Facebook channel integration within Dynamics 365 Customer Service.

Facebook settings should have all required fields¶

Facebook channel integration in Dynamics 365 Customer Service requires specific configuration settings to be defined. Missing required fields in the Facebook channel settings can prevent the channel from functioning correctly. The Solution Health Hub verifies that Facebook channel settings have all the necessary fields populated, specifically checking for the messaging endpoint URL field.

This check focuses on the configuration details of the Facebook channel and verifies that Facebook channel settings have the messaging endpoint URL field. The messaging endpoint URL is a critical configuration parameter that tells Dynamics 365 how to communicate with the Facebook Messenger platform. Without a valid messaging endpoint URL, Dynamics 365 cannot send or receive messages through the Facebook channel.

If the Solution Health Hub flags this issue, it indicates that the messaging endpoint URL field is missing or empty in the settings for the Facebook channel. To resolve this, edit the Facebook channel settings and ensure that the messaging endpoint URL field is populated with the correct URL for the Facebook Messenger endpoint. Obtain the correct messaging endpoint URL from Facebook’s developer documentation or configuration settings for your Facebook app integration. Verifying and populating all required fields, especially the messaging endpoint URL, is crucial for ensuring that the Facebook channel can establish communication and function correctly within Dynamics 365 Customer Service.

Line channel configuration should have work stream¶

LINE is another popular messaging platform, and Dynamics 365 Customer Service allows integration with LINE channels through Omnichannel. Similar to Facebook, LINE channels need to be associated with an active work stream to function within Omnichannel. The Solution Health Hub verifies that all configured LINE channel configurations have an active work stream.

This check ensures that each LINE channel configuration for Omnichannel integration is linked to an active work stream. Verifies that all LINE channel configurations have an active work stream. Work streams are essential for routing and processing interactions from LINE channels. Without an active work stream, LINE messages cannot be properly managed within Omnichannel, and the LINE channel integration will be ineffective.

If the Solution Health Hub flags this issue, it indicates that one or more LINE channel configurations are missing an active work stream association. To resolve this, navigate to the LINE channel configuration settings in Omnichannel and associate each channel with an active work stream. If a suitable work stream does not exist, you might need to create a new work stream specifically for LINE interactions. Ensure that the selected work stream is active and configured to handle LINE messages appropriately. Refer to the documentation on “Configure a LINE channel” for guidance on setting up LINE channels and work stream associations. Linking LINE channels to active work streams is essential for enabling effective LINE channel integration within Dynamics 365 Customer Service.

Line settings should have all required fields¶

LINE channel integration in Dynamics 365 Customer Service requires specific configuration settings to be defined. Missing required fields in the LINE channel settings can prevent the channel from functioning correctly. The Solution Health Hub verifies that the LINE settings have all necessary fields populated, specifically checking if the webhook URL is not empty.

This check focuses on the configuration details of the LINE channel and verifies that the LINE settings webhook URL isn’t empty. The webhook URL is a critical configuration parameter that tells the LINE platform where to send messages and events to Dynamics 365. If the webhook URL is empty, LINE cannot send messages to Dynamics 365, and the channel will not function.

If the Solution Health Hub flags this issue, it indicates that the webhook URL field is missing or empty in the settings for the LINE channel. To resolve this, edit the LINE channel settings and ensure that the webhook URL field is populated with the correct URL for your Dynamics 365 Omnichannel instance. Obtain the correct webhook URL from your Dynamics 365 Omnichannel configuration or setup documentation. Verifying and populating all required fields, especially the webhook URL, is crucial for ensuring that the LINE channel can establish communication and function correctly within Dynamics 365 Customer Service.

Live chat channel configuration should have work stream¶

Live chat is a core channel in Dynamics 365 Customer Service, enabling real-time interactions with customers through chat widgets. For live chat to function within Omnichannel, it must be associated with an active work stream. The Solution Health Hub verifies that Live Chat has an active work stream configured.

This check ensures that the Live Chat channel configuration is linked to an active work stream. Verifies that Live Chat has an active work stream. Work streams are essential for routing and managing incoming chat requests. Without an active work stream, live chat requests cannot be properly routed to agents within Omnichannel, and the live chat functionality will be ineffective.

If the Solution Health Hub flags this issue, it indicates that the Live Chat channel configuration is missing an active work stream association. To resolve this, navigate to the Live Chat channel configuration settings in Omnichannel and associate it with an active work stream. If a suitable work stream does not exist, you might need to create a new work stream specifically for live chat interactions. Ensure that the selected work stream is active and configured to handle chat requests appropriately. Refer to the documentation on “Configure a chat channel” for guidance on setting up live chat channels and work stream associations. Linking Live Chat to an active work stream is essential for enabling effective live chat functionality within Dynamics 365 Customer Service.

Omnichannel service endpoint should be configured¶

Omnichannel for Customer Service relies on underlying services to function correctly. If these services are not properly configured or provisioned, Omnichannel features will not work. The Solution Health Hub includes a critical check to ensure that the Omnichannel service endpoint is configured correctly.

This check verifies the overall provisioning and configuration of the underlying services required for Omnichannel. Verifies that the underlying services needed for the functioning of Omnichannel for Customer Service are configured correctly. This check is a high-level validation to ensure that the foundational infrastructure for Omnichannel is in place. If the service endpoint is not configured, it indicates a broader provisioning or setup issue with Omnichannel.

If the Solution Health Hub flags this issue, it signifies a fundamental problem with the Omnichannel service configuration. To resolve this, you likely need to review the Omnichannel provisioning and setup process. Ensure that Omnichannel for Customer Service has been correctly provisioned within your Dynamics 365 environment and that all necessary service components are properly configured and running. Refer to the documentation on “Provisioning Omnichannel for Customer Service” for detailed steps on provisioning and setting up Omnichannel. Correctly configuring the Omnichannel service endpoint is a prerequisite for using any Omnichannel features in Dynamics 365 Customer Service.

Queues should have agents¶

Queues are used in Dynamics 365 Customer Service to organize and distribute work items to agents. For queues to be effective in routing work, they need to have agents assigned to them. The Solution Health Hub verifies that queues assigned to work streams have agents associated with them.

This check ensures that queues that are used for routing work items within work streams have at least one agent assigned. Verifies that the queues that are assigned to the work streams have agents assigned. Queues without agents are essentially dead ends for work items. If a work item is routed to a queue with no agents, it will remain unassigned and will not be processed, leading to delays in customer service.

If the Solution Health Hub flags this issue, it indicates that one or more queues assigned to work streams are missing agent assignments. To resolve this, review the queue configurations for the identified queues and assign agents to them. Agents can be added to queues through queue management settings in Dynamics 365. Ensure that appropriate agents with the necessary skills and capacity are assigned to each queue to handle the expected workload. Refer to the documentation on “Manage queues” for guidance on queue management and agent assignment. Assigning agents to queues is essential for enabling effective work item routing and processing within Dynamics 365 Customer Service.

SDK message/plugins should be active¶

SDK messages and plugins are core components of Dynamics 365, enabling custom code execution in response to system events. Customer Service relies on specific SDK messages and plugins for its intended functionality. If these are deactivated or disabled, it can disrupt Customer Service operations. The Solution Health Hub verifies that the SDK messages and plugins required for Customer Service are active.

This check ensures that the necessary SDK messages or plugins for Customer Service are in an active state. Verifies that the SDK messages or plug-ins are active. Deactivated or disabled SDK messages and plugins will not execute their associated custom code, potentially breaking or degrading Customer Service features that rely on this code.

If the Solution Health Hub flags this issue, it indicates that some SDK messages or plugins required for Customer Service are deactivated or disabled. To resolve this, review the list of deactivated or disabled SDK messages/plugins identified by the Solution Health Hub and reactivate them. SDK messages and plugins can be managed within the customization area of Dynamics 365. Before reactivating, consider if there was a specific reason for deactivation and if reactivation aligns with your intended system configuration. Generally, system-provided SDK messages and plugins for Customer Service should remain active in production environments. Refer to the documentation on “Remove deactivated or disabled customizations” for best practices related to managing customizations. Keeping essential SDK messages and plugins active is crucial for maintaining the intended functionality of Dynamics 365 Customer Service.

SMS channel configuration should have work stream¶

SMS (Short Message Service) is a widely used communication channel, and Dynamics 365 Customer Service allows integration with SMS channels through Omnichannel. For SMS channels to be managed within Omnichannel, they need to be associated with an active work stream. The Solution Health Hub verifies that the SMS channel has an active work stream configured.

This check ensures that the SMS channel configuration for Omnichannel integration is linked to an active work stream. Verifies that the SMS channel has an active work stream. Work streams are essential for routing and processing SMS messages. Without an active work stream, SMS messages cannot be properly routed to agents within Omnichannel, and the SMS channel integration will be ineffective.

If the Solution Health Hub flags this issue, it indicates that the SMS channel configuration is missing an active work stream association. To resolve this, navigate to the SMS channel configuration settings in Omnichannel and associate it with an active work stream. If a suitable work stream does not exist, you might need to create a new work stream specifically for SMS interactions. Ensure that the selected work stream is active and configured to handle SMS messages appropriately. Refer to the documentation on “Configure an SMS channel for TeleSign” and “Configure an SMS channel for Twilio” for guidance on setting up SMS channels and work stream associations, depending on your SMS provider. Linking the SMS channel to an active work stream is essential for enabling effective SMS channel integration within Dynamics 365 Customer Service.

SMS settings should have all required fields¶

SMS channel integration in Dynamics 365 Customer Service requires specific configuration settings to be defined. Missing required fields in the SMS channel settings can prevent the channel from functioning correctly. The Solution Health Hub verifies that SMS settings have all the necessary fields populated, specifically checking that the customer ID and API key fields are not empty.

This check focuses on the configuration details of the SMS channel and verifies that SMS settings don’t have empty customer ID and API key fields. The customer ID and API key are essential credentials provided by your SMS provider (e.g., TeleSign, Twilio) that authenticate Dynamics 365 to use their SMS services. Without valid customer ID and API key values, Dynamics 365 cannot connect to the SMS provider and send or receive SMS messages.

If the Solution Health Hub flags this issue, it indicates that either the customer ID or API key field (or both) is missing or empty in the settings for the SMS channel. To resolve this, edit the SMS channel settings and ensure that both the customer ID and API key fields are populated with the correct credentials provided by your SMS provider. Obtain these credentials from your SMS provider account or configuration documentation. Verifying and populating all required fields, especially the customer ID and API key, is crucial for ensuring that the SMS channel can establish communication with the SMS provider and function correctly within Dynamics 365 Customer Service.

Teams channel configuration should have work stream¶

Microsoft Teams is a widely used collaboration platform, and Dynamics 365 Customer Service offers integration with Teams channels through Omnichannel. For Teams channels to be managed within Omnichannel, they need to be associated with an active work stream. The Solution Health Hub verifies that the Microsoft Teams channel configuration has an active work stream.

This check ensures that the Microsoft Teams channel configuration for Omnichannel integration is linked to an active work stream. Verifies that the Microsoft Teams channel configuration has an active work stream. Work streams are essential for routing and processing conversations from Teams channels. Without an active work stream, Teams messages cannot be properly routed to agents within Omnichannel, and the Teams channel integration will be ineffective.

If the Solution Health Hub flags this issue, it indicates that the Microsoft Teams channel configuration is missing an active work stream association. To resolve this, navigate to the Microsoft Teams channel configuration settings in Omnichannel and associate it with an active work stream. If a suitable work stream does not exist, you might need to create a new work stream specifically for Teams interactions. Ensure that the selected work stream is active and configured to handle Teams messages appropriately. Refer to the documentation on “Configure a Microsoft Teams channel” for guidance on setting up Teams channels and work stream associations. Linking the Teams channel to an active work stream is essential for enabling effective Microsoft Teams channel integration within Dynamics 365 Customer Service.

Teams settings should have all required fields¶

Microsoft Teams channel integration in Dynamics 365 Customer Service requires specific configuration settings to be defined. Missing required fields in the Teams channel settings can prevent the channel from functioning correctly. The Solution Health Hub verifies that Teams settings have all necessary fields populated, specifically checking that the bot ID field is not missing.

This check focuses on the configuration details of the Teams channel and verifies that the bot ID field isn’t missing from the Teams settings. The bot ID is a crucial identifier for the bot that facilitates communication between Dynamics 365 and Microsoft Teams. Without a valid bot ID, Dynamics 365 cannot properly integrate with the Teams channel and route messages.

If the Solution Health Hub flags this issue, it indicates that the bot ID field is missing or empty in the settings for the Teams channel. To resolve this, edit the Teams channel settings and ensure that the bot ID field is populated with the correct bot ID for your Teams integration. Obtain the correct bot ID from your Teams bot configuration or setup documentation. Verifying and populating all required fields, especially the bot ID, is crucial for ensuring that the Teams channel can establish communication and function correctly within Dynamics 365 Customer Service.

WeChat channel configuration should have work stream¶

WeChat is a popular messaging platform, especially in certain regions, and Dynamics 365 Customer Service offers integration with WeChat channels through Omnichannel. For WeChat channels to be managed within Omnichannel, they need to be associated with an active work stream. The Solution Health Hub verifies that all configured WeChat channel configurations have an active work stream.

This check ensures that each WeChat channel configuration for Omnichannel integration is linked to an active work stream. Verifies that all WeChat channel configurations have an active work stream. Work streams are essential for routing and processing interactions from WeChat channels. Without an active work stream, WeChat messages cannot be properly managed within Omnichannel, and the WeChat channel integration will be ineffective.

If the Solution Health Hub flags this issue, it indicates that one or more WeChat channel configurations are missing an active work stream association. To resolve this, navigate to the WeChat channel configuration settings in Omnichannel and associate each channel with an active work stream. If a suitable work stream does not exist, you might need to create a new work stream specifically for WeChat interactions. Ensure that the selected work stream is active and configured to handle WeChat messages appropriately. Refer to the documentation on “Configure a WeChat channel” for guidance on setting up WeChat channels and work stream associations. Linking WeChat channels to active work streams is essential for enabling effective WeChat channel integration within Dynamics 365 Customer Service.

WeChat settings should have all required fields¶

WeChat channel integration in Dynamics 365 Customer Service requires specific configuration settings to be defined. Missing required fields in the WeChat channel settings can prevent the channel from functioning correctly. The Solution Health Hub verifies that the WeChat settings have all necessary fields populated, specifically checking that the IP allowlist and Server address (URL) fields are not empty.

This check focuses on the configuration details of the WeChat channel and verifies that the IP allowlist and Server address (URL) fields aren’t empty in the WeChat settings. The IP allowlist and Server address (URL) are crucial security and communication parameters for WeChat integration. The IP allowlist restricts access to the WeChat integration to specific IP addresses, and the Server address (URL) defines the endpoint for communication between Dynamics 365 and WeChat. Without valid values in these fields, WeChat integration will likely fail or be insecure.

If the Solution Health Hub flags this issue, it indicates that either the IP allowlist or Server address (URL) field (or both) is missing or empty in the settings for the WeChat channel. To resolve this, edit the WeChat channel settings and ensure that both the IP allowlist and Server address (URL) fields are populated with the correct values. Obtain these values from your WeChat developer account or configuration documentation, ensuring the IP allowlist is correctly configured for security and the Server address (URL) points to your Dynamics 365 Omnichannel instance. Verifying and populating all required fields, especially the IP allowlist and Server address (URL), is crucial for ensuring that the WeChat channel can establish secure communication and function correctly within Dynamics 365 Customer Service.

WhatsApp channel configuration should have work stream¶

WhatsApp is a globally popular messaging platform, and Dynamics 365 Customer Service offers integration with WhatsApp channels through Omnichannel. For WhatsApp channels to be managed within Omnichannel, they need to be associated with an active work stream. The Solution Health Hub verifies that all configured WhatsApp phone numbers have an active work stream.

This check ensures that each WhatsApp phone number configured for Omnichannel integration is linked to an active work stream. Verifies that all WhatsApp phone numbers have an active work stream. Work streams are essential for routing and processing interactions from WhatsApp channels. Without an active work stream, WhatsApp messages cannot be properly managed within Omnichannel, and the WhatsApp channel integration will be ineffective.

If the Solution Health Hub flags this issue, it indicates that one or more WhatsApp phone numbers are missing an active work stream association. To resolve this, navigate to the WhatsApp channel configuration settings in Omnichannel and associate each phone number with an active work stream. If a suitable work stream does not exist, you might need to create a new work stream specifically for WhatsApp interactions. Ensure that the selected work stream is active and configured to handle WhatsApp messages appropriately. Refer to the documentation on “Configure a WhatsApp channel” for guidance on setting up WhatsApp channels and work stream associations. Linking WhatsApp phone numbers to active work streams is essential for enabling effective WhatsApp channel integration within Dynamics 365 Customer Service.

WhatsApp settings should have all required fields¶

WhatsApp channel integration in Dynamics 365 Customer Service requires specific configuration settings to be defined. Missing required fields in the WhatsApp channel settings can prevent the channel from functioning correctly. The Solution Health Hub verifies that WhatsApp settings have all necessary fields populated, specifically checking for a valid Twilio inbound URL and validation status.

This check focuses on the configuration details of the WhatsApp channel and verifies that WhatsApp settings have a valid Twilio inbound URL and validation hasn’t failed. The Twilio inbound URL is a critical configuration parameter for WhatsApp integration, as Twilio is a common provider for WhatsApp Business API access. The inbound URL tells Twilio where to send incoming WhatsApp messages to Dynamics 365. Additionally, the validation status check ensures that the inbound URL has been successfully validated by Twilio. Without a valid and validated Twilio inbound URL, WhatsApp integration will not function.

If the Solution Health Hub flags this issue, it indicates that either the Twilio inbound URL is missing, invalid, or validation has failed in the WhatsApp channel settings. To resolve this, edit the WhatsApp channel settings and ensure that the Twilio inbound URL field is populated with the correct and valid URL for your Dynamics 365 Omnichannel instance, and that the validation process is successful. Obtain the correct inbound URL from your Dynamics 365 Omnichannel configuration or setup documentation, and follow the validation process outlined in the documentation to ensure Twilio can successfully connect to your Dynamics 365 instance. Verifying and ensuring a valid and validated Twilio inbound URL is crucial for enabling WhatsApp channel communication within Dynamics 365 Customer Service.

Work stream capacity should be less than agents¶

Capacity management in Dynamics 365 Customer Service involves both agent capacity and work stream capacity. Work stream capacity defines the total capacity allocated to a specific work stream, while agent capacity defines the individual capacity of each agent. For effective workload distribution, the total agent capacity assigned to a work stream should be greater than the work stream capacity. The Solution Health Hub verifies this capacity relationship.

This check ensures that the total capacity of agents assigned to a work stream is greater than the capacity defined for the work stream itself. Verifies that the capacity defined for agents is more than that defined for the work streams. If the work stream capacity is greater than the agent capacity, it can lead to situations where the work stream becomes overloaded, and agents are unable to handle the incoming workload effectively. This can result in delays, missed interactions, and inefficient resource utilization.

If the Solution Health Hub flags this issue, it indicates a potential capacity imbalance between work streams and agents. To resolve this, review the capacity settings for the identified work streams and the agents assigned to them. Increase the total capacity of agents assigned to the work stream so that it exceeds the work stream capacity. You can achieve this by either increasing the capacity of existing agents or by assigning more agents to the work stream. Refer to the documentation on “Understand work streams” for more information on work stream and agent capacity management. Ensuring that agent capacity exceeds work stream capacity is crucial for maintaining balanced workload distribution and optimal performance within Dynamics 365 Customer Service.

Work stream should have notification templates set¶

Notification templates are used in Dynamics 365 Customer Service to send notifications to agents when new work items are routed to them. For agents to receive these notifications, work streams need to have notification templates set. The Solution Health Hub verifies that notification templates are set for work streams.

This check ensures that each work stream has at least one notification template associated with it. Verifies that notification templates have been set for work streams. Notification templates define the content and format of notifications sent to agents. Without notification templates, agents will not receive timely alerts when new work items are routed to them, potentially leading to missed interactions and delayed response times.

If the Solution Health Hub flags this issue, it indicates that one or more work streams are missing notification template configurations. To resolve this, navigate to the work stream settings for the identified work streams and configure notification templates. You can associate existing notification templates or create new templates as needed. Ensure that appropriate notification templates are set for each work stream to enable agents to receive timely alerts for new work items. Refer to the documentation on “Associate templates with work streams” for guidance on setting up notification templates for work streams. Configuring notification templates is essential for enabling proactive agent notifications and improving response times in Dynamics 365 Customer Service.

Work stream should have session template set¶

Session templates in Dynamics 365 Customer Service define the layout and configuration of agent sessions when they handle customer interactions. For agents to have consistent and optimized session experiences, work streams need to have session templates set. The Solution Health Hub verifies that session templates are set for work streams.

This check ensures that each work stream has at least one session template associated with it. Verifies that session templates have been set for work streams. Session templates define the applications, tabs, and layouts that agents see when they open a session to handle a work item. Without session templates, agents might have a less organized and less efficient session experience, potentially impacting their productivity and the quality of customer service.

If the Solution Health Hub flags this issue, it indicates that one or more work streams are missing session template configurations. To resolve this, navigate to the work stream settings for the identified work streams and configure session templates. You can associate existing session templates or create new templates tailored to the specific needs of each work stream. Ensure that appropriate session templates are set for each work stream to provide agents with optimized and consistent session experiences. Refer to the documentation on “Associate templates with work streams” for guidance on setting up session templates for work streams. Configuring session templates is essential for enhancing agent productivity and ensuring a consistent and efficient agent experience in Dynamics 365 Customer Service.

Work stream shouldn’t have duplicate context variables¶

Context variables in Dynamics 365 Customer Service allow you to pass information between different components of the system, such as between work streams and agent scripts. Within a work stream, each context variable should be uniquely defined. Duplicate context variables within a work stream can lead to confusion and unexpected behavior. The Solution Health Hub verifies that work streams do not have duplicate context variables.

This check ensures that within each work stream, all defined context variables have unique names. Verifies that duplicate context variables haven’t been defined for work streams. Duplicate context variables can create ambiguity and make it difficult to correctly access and use context data within work streams and related components. This can lead to errors in routing, agent scripting, and other processes that rely on context variables.

If the Solution Health Hub flags this issue, it indicates that one or more work streams have duplicate context variables defined. To resolve this, review the context variable configurations for the identified work streams and remove or rename any duplicate context variables. Ensure that each context variable within a work stream has a unique and descriptive name. Refer to the documentation on “Create a work stream” for guidance on defining context variables. Eliminating duplicate context variables is essential for maintaining data integrity and ensuring predictable behavior within Dynamics 365 Customer Service.

Work stream shouldn’t have empty routing rules above rules with condition¶

Routing rules in Dynamics 365 Customer Service define how work items are routed to agents. Routing rules are processed in order of priority. Having empty routing rules (rules with no conditions) positioned above rules with conditions can prevent the conditional rules from ever being evaluated. The Solution Health Hub verifies that work streams do not have empty routing rules positioned above conditional rules.

This check ensures that within each work stream, if there are routing rules with conditions, there are no empty routing rules with a higher priority. Verifies that empty routing rules haven’t been defined for a work stream that prevents routing rules with a lower priority from running. An empty routing rule, by definition, matches all incoming work items. If an empty rule has a higher priority than a rule with specific conditions, all work items will match the empty rule first and be routed according to that rule, effectively bypassing the conditional rules with lower priority. This can lead to incorrect routing and prevent work items from being routed to the intended agents based on specific conditions.

If the Solution Health Hub flags this issue, it indicates that one or more work streams have empty routing rules positioned above conditional rules. To resolve this, review the routing rule configurations for the identified work streams and adjust the priority of routing rules. Either remove the empty routing rule if it’s not needed, or lower its priority so that conditional rules with specific routing criteria are evaluated first. Ensure that the routing rule order and priorities are configured to correctly implement your intended routing logic, allowing conditional rules to be evaluated and applied when appropriate. Refer to the documentation on “Create and manage routing rules” for guidance on configuring routing rules and priorities. Properly ordering and prioritizing routing rules is crucial for ensuring accurate and condition-based work item routing within Dynamics 365 Customer Service.

---

If you have any questions or require further clarification on these troubleshooting tips, please feel free to leave a comment below. Your feedback and interactions are valuable!