---
title: Monitor Alerts
excerpt: ''
deprecated: false
hidden: false
metadata:
  title: ''
  description: ''
  robots: index
next:
  description: ''
---
## What are Moveworks Alerts?

Moveworks Alerts inform administrators of critical events within the customer instance that may impact skill functionality. These notifications enable rapid detection and response to potential issues, helping you maintain system health and resolve problems efficiently.

<Callout intent="info">
  Alerts are by default available in Moveworks Setup Alerts module. To enable in-bot alert notifications (Beta), please reach out to your Customer Success Manager or support team.
</Callout>

### How to navigate in Moveworks Setup?

1. Open Moveworks Setup.
2. Navigate to Organization Details > Alerts

![](https://files.readme.io/74943e5b319779ad16caa7185590ea9841a1a4e888ce2a910724984a5a5f8c17-image.png)

### Columns in Alerts home screen

* **Module**: The segment of the system where the alert originates.
* **Alert ID**: A unique identifier assigned to each alert.
* **Alert Name**: The title that describes the essence of the alert.
* **Alert Description**: A brief explanation providing context to the alert.
* **Alert Type**: The category that the alert falls into
  * System Alert: Integration specific alerts
  * Configuration Alert: Alerts generating from configuration changes
  * External Alert: Alerts originating from external chat system
* **Last Fired at**: The most recent time and date when the alert was last triggered.
* **Total Times fired**: Count of times the same alert was fired.
* **Active Since**: Time from which a specific alert is active.
* **Acknowledged By**: User who is acknowledging an active alert in the UI.

There are 2 states a alert can be present in

1. **Active** - Active alerts signifying that the issue is possibly still persisting
2. **Archived** - Historical alerts that were triggered and resolved.
   1. An Alert gets moved to the Archived section if alert expression criteria is resolved internally.
   2. The archived alerts section contains a history of the last 2 months of alerts.

### Supported Alert Types

Moveworks Alerts infrastructure is evolving. Currently Moveworks support a limited number of alerts covering few scenarios that impacts a skill functioning.

<Table align={["left","left","left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Module
      </th>

      <th>
        Alert Name
      </th>

      <th>
        Alert Type
      </th>

      <th>
        Alert Description
      </th>

      <th>
        Downstream Alert Impact
      </th>

      <th>
        Troubleshooting Docs or Recommended Steps
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Connector
      </td>

      <td>
        Integration Failure - \{System}
      </td>

      <td>
        System Alert
      </td>

      <td>
        System is failing to connect with \{System}. Please check credentials and the authentication system used
      </td>

      <td>
        Import Users, Account Access, Group Access,  Employee Comms
      </td>

      <td>
        Ensure the Connector has been setup Following the Steps [here](/docs/access-requirements)
      </td>
    </tr>

    <tr>
      <td>
        Identity
      </td>

      <td>
        User validation failed
      </td>

      <td>
        Configuration Alert
      </td>

      <td>
        User identity validation failed.
      </td>

      <td>
        If not fixed over time this will impact : Import Users, Ticketing, Knowledge Search, File Search, Account Access, Group Access,  Employee Comms
      </td>

      <td>
        The issue is commonly due to the Integrations not having the same Joining Key, Please ensure the step [here](/docs/mw-setup-identity#/step-3-set-join-key) has been followed when configuring Identity.
      </td>
    </tr>

    <tr>
      <td>
        Ticketing
      </td>

      <td>
        Ticketing - Tickets are not passing the Universal ticket filter
      </td>

      <td>
        Ticketing Filter Alert
      </td>

      <td>
        No tickets have passed universal filter. Check ticket filters (particularly Universal ticket fetching filter)
      </td>

      <td>
        Ticketing, Ticket Actions, Ticket Polling, Ticket Interception
      </td>

      <td>
        Learn more about how Ticket Filters are setup [here](/docs/ticket-filters#/universal-ticket-fetching-filter).
      </td>
    </tr>

    <tr>
      <td>
        Internal Knowledge
      </td>

      <td>
        Knowledge Ingestion - Large drop in articles
      </td>

      <td>
        Configuration Alert
      </td>

      <td>
        A significant (>50%) decrease in the number of ingested articles has been detected.
      </td>

      <td>
        Internal Knowledge would have a gap in content.
      </td>

      <td>
        1. If this drop is expected, contact Moveworks Support and request: "Mark ingestion of knowledge articles as healthy despite large data drop".
        2. Check for intentional config changes
        3. Verify source system health
        4. Check connector permissions
      </td>
    </tr>

    <tr>
      <td>
        Agent
      </td>

      <td>
        Agent disconnected
      </td>

      <td>
        External Alert
      </td>

      <td>
        There are no Moveworks on-prem agents connected.
      </td>

      <td>
        Import Users, Account Access, Group Access,  Employee Comms
      </td>

      <td>
        Please follow [this Troubleshooting Document](/docs/moveworks-agent-troubleshooting#/handy-docker-commands-when-debugging) for steps to Resolution
      </td>
    </tr>

    <tr>
      <td>
        Connector
      </td>

      <td>
        Chat credentials expired
      </td>

      <td>
        System Alert
      </td>

      <td>
        Chat system responded with "401 - Unauthorized". This means that the existing credentials are no longer valid and the bot is unable to send messages to the users.
      </td>

      <td>
        Bot Unresponsive to user/users in the Chat Interaction Platform.
      </td>

      <td>
        Credentials Rotation Guide for :
        [Microsoft Teams](/docs/microsoft-teams-secret-rotation-guide)
        [Slack](/docs/slack-bot-setup-guide#/bot-creation)
      </td>
    </tr>

    <tr>
      <td>
        Chat
      </td>

      <td>
        Bot has been disabled by admin
      </td>

      <td>
        External Alert
      </td>

      <td>
        The bot has been disabled and is unable to send messages to users and/or users may be unable to locate the bot in their chat client. Please reach out to your Microsoft Teams admin to get the bot re-enabled in your Teams admin console. This may also require modifying the app's Permission Policy.
      </td>

      <td>
        Bot Unavailable to user/users in the Chat Interaction Platform.
      </td>

      <td>
        Please reach out to your Microsoft Teams admin to get the bot re-enabled in your Teams admin console. This may also require modifying the app's Permission Policy.
      </td>
    </tr>

    <tr>
      <td>
        Connector
      </td>

      <td>
        ServiceNow Service Account Timezone Mismatch
      </td>

      <td>
        System Alert
      </td>

      <td>
        The timezone of the ServiceNow service account configured as a Moveworks connector does not match one of the expected timezones ('GMT', 'GMT0', 'UTC', 'America/Danmarkshavn').
      </td>

      <td>
        In Ticketing > Ticket Polling would be unable to poll tickets due to the invalid timezone.
      </td>

      <td>
        [Here](/docs/servicenow-access-requirements#/service-account-requirements--permissions) are the steps to setup the Time Zone.
      </td>
    </tr>

    <tr>
      <td>
        Connector
      </td>

      <td>
        Microsoft Teams - Message Authentication Failure
      </td>

      <td>
        System Alert
      </td>

      <td>
        Failure to authenticate Microsoft Teams inbound messages
      </td>

      <td>
        Bot Unresponsive to user/users in the Chat Interaction Platform.
      </td>

      <td>
        Reach out to the Moveworks Support Team
      </td>
    </tr>

    <tr>
      <td>
        Connector
      </td>

      <td>
        Microsoft Teams Installation Forbidden
      </td>

      <td>
        System Alert
      </td>

      <td>
        Failure to install bot in Microsoft Teams to subset of users.
      </td>

      <td>
        Microsoft Teams - Bot installation blocked for some users
      </td>

      <td>
        1. Have your Microsoft Teams Admin confirm the bot is assigned and authorized for the necessary permissions (User.Read.All & TeamsAppInstallation.ReadWriteSelfForUser.All)
        2. Review the app permission policy settings for the bot.
        3. Verify that the bot has not been blocked or restricted by organizational policies.
      </td>
    </tr>

    <tr>
      <td>
        Permissions
      </td>

      <td>
        ServiceNow Permissions Data Stale
      </td>

      <td>
        System Alert
      </td>

      <td>
        Moveworks ServiceNow User Criteria Ingestion is failing
      </td>

      <td>
        ServiceNow Knowledge may not serve to users
      </td>

      <td>
        1. Verify connector is properly Configured
        2. Verify Moveworks acl Update set is properly installed
        3. Confirm that the moveworks_user role in ServiceNow must be granted to the Moveworks service account

        After confirming above, file a Moveworks Support ticket.
      </td>
    </tr>

    <tr>
      <td>
        Access Groups
      </td>

      <td>
        Group ingestion Failure
      </td>

      <td>
        System Alert
      </td>

      <td>
        Issues importing Groups into Moveworks
      </td>

      <td>
        Groups leveraged in the Access DL skill may not be able to discover new Groups
      </td>

      <td>
        1. Verify connector has the right scopes
        2. Check with your IDAM team if there is issues with the system.
      </td>
    </tr>

    <tr>
      <td>
        Internal Knowledge
      </td>

      <td>
        Knowledge Ingestion Failure
      </td>

      <td>
        System Alert
      </td>

      <td>
        Knowledge data is stale due to a downstream error or other restriction such as Large Data Change Protection being triggered.
      </td>

      <td>
        Moveworks AI Assistant will not be able to answer questions related to new
      </td>

      <td>
        1. Verify the connector has the right scopes and the credentials are correct.
        2. Check with your Knowledge team if there is issues with the specific system.
        3. Navigate to Core Platform > Customer Data Ingestion, to view the knowledge ingestion, Click `View Logs`for further info, ensure to review the **Error Summary**.
        4. Email Moveworks Support to mark the Ingestion as approved if it is due to a Large Data Change Protection alert.
      </td>
    </tr>

    <tr>
      <td>
        Group Identity Stale
      </td>

      <td>
        Group Ingestion Failure
      </td>

      <td>
        System Alert
      </td>

      <td>
        Group Ingestion data is stale due to a downstream error or other restriction such as Large Data Change Protection being triggered.
      </td>

      <td>
        Groups leveraged in the Access DL skill may not be able to discover new Groups
      </td>

      <td>
        1. Verify connector has the right scopes and the credentials are correct
        2. Check with your IDAM team if there is issues with the system.
        3. Email Moveworks Support to mark the Ingestion as approved if it is due to a Large Data Change Protection alert.
      </td>
    </tr>

    <tr>
      <td>
        User Identity Stale
      </td>

      <td>
        User Ingestion Failure
      </td>

      <td>
        System Alert
      </td>

      <td>
        User Identity data is stale due to a downstream error or other restriction
      </td>

      <td>
        New employees may not be able to use the Moveworks Assistant.
      </td>

      <td>
        1. Navigate to Core Platform > Customer Data Ingestion, see which connector is failing
        2. Verify connector has the right scopes and the credentials are correct.
        3. Click `View Logs`for further info, ensure to review the **Error Summary**.
      </td>
    </tr>

    <tr>
      <td>
        Form Data Stale
      </td>

      <td>
        Form Ingestion Failure
      </td>

      <td>
        System Alert
      </td>

      <td>
        Forms are stale due to a downstream error or other restriction
      </td>

      <td>
        New forms may not surface from within the Moveworks Assistant.
      </td>

      <td>
        1. If this drop is expected, please contact Moveworks Support and request: "Mark ingestion of Forms as healthy despite large data drop"
        2. Ensure the external data source that forms are being imported from is online and accessible.
        3. Confirm that the Moveworks service account or equivalent API credential has the correct permissions and access scopes to import forms.
      </td>
    </tr>
  </tbody>
</Table>

<br />