Scheduled Alert Errors and Meanings

Prev Next

This article will detail error messages and the reasoning behind the error messages while scheduling an alert to be sent.

A Scheduled Alert Will Show Up in an Error State in the User Interface

  • Both the list view and the detail view will show the scheduled alert in an error state

  • An alert in this state won't go out until the user edits the alert

Alert Validation Errors

  • Unable to find alert requests for scheduled settings

    • This means the necessary record for the scheduled alert is missing

    • No message will appear in the User Interface (UI) but will be found in the database

  • Unable to find scheduled settings {0}

    • This means the record for the scheduled alert is missing

    • No message will appear in the UI but will be found in the database

  • Scheduled alert is disabled

    • This means a necessary record for the scheduled alert is missing

    • No message will appear in the UI but will be found in the database

      Note:

      Detail view will show an error message and show the reason why the alert failed in the History list

  • Alert has no end date

    • This means the scheduled alert has no end date

    • The scheduled alert will show in the UI

    • The user must edit the alert to fix the error

  • End date is past the current date

    • This means the scheduled alert end date was more than three hours in the past when the alert was sent

    • The scheduled alert will show in the UI

    • The user must edit the alert to fix the error

  • Scheduled alert has already been processed

    • This means the scheduled alert has already been processed for the current execution date

    • The scheduled alert will show in the UI

    • The user must edit the alert to fix the error

  • Alert sent outside allowed time buffer

    • This means the scheduled alert was sent more than three hours after the Next Execution Date

    • The scheduled alert will show in the UI

    • The user must edit the alert to fix the error

  • Recurring alert next execution date is in the future

    • This means the Next Execution Date is in the future

    • This will only show up when a super admin triggers a recurring alert before its Next Execution Date

    • This will not put the alert into an error state

  • The administrator who created this scheduled alert no longer exists

    • This means the original Admin that created the alert no longer exists

    • A new Admin in the tenant needs to edit the scheduled alert and reschedule it

  • Error reading recurring data

    • This means the recurring data for the alert was corrupted

    • An Admin for the tenant needs to edit the alert and reschedule it

    • Full exception will be logged so a super admin can see what caused the error

  • This alert is locked for processing. To unlock it, edit the alert.

    • This means another process tried to process an alert that has already been processed for the current execution time.

    • An Admin will need to edit the alert to unlock it. The lock will be removed after one hour by the system.

  • Send Alert Error

    • Any system errors thrown at send time will be recorded in the logs and the Scheduled Alert History table.

    • An Admin will need to edit the alert to fix the error or contact customer support.