Error reference（错误参考）¶
:::callout{theme="warning"} Object Monitors are superseded by Automate. Automate is a fully backward-compatible product that offers a single entry point for all business automation in the platform. :::
This page describes some of the common error categories that may be encountered when using the Object Monitors application or the Monitors view in Object Explorer.
Evaluation errors¶
A monitor may fail to evaluate due to problems with the underlying data. Monitors are automatically retried, but some errors may require manual intervention. For example, if the object type being monitored is deleted, monitors using inputs containing objects of that type will fail to evaluate.
Monitor out of sync¶
Object monitors use a reference to a saved exploration to define the input. This reference is not dynamic, but instead is stored according to the exploration as it exists when the monitor is saved. If the exploration changes, the monitor will continue to evaluate using the exploration's old state unless the monitor is updated. In this case, a warning banner is displayed on the monitor:
Notification effect errors¶
After a successful monitor evaluation, notifications may fail to send. If this occurs, the history event will show a tag indicating that notifications for that event were not sent to subscribers, along with additional details such as an error identifier and error message.
Action effect errors¶
After a successful monitor evaluation, Action effects may fail to execute. This failure could happen for a variety of reasons, including changes to the Action logic that make it incompatible with the saved input configuration on the monitor, or because the submission criteria for the Action is not met. If this failure occurs, the history event timeline will show a tag indicating that one or more Actions failed to execute for that event, along with relevant error details.
Permissions¶
Monitor evaluation uses the permissions of the individual subscribers. This is to ensure that monitor evaluation and any subsequent Action or notification effects will always reflect data that the user may access at the time the monitor is evaluated. If a user is missing permission to view the input object type(s), saved exploration(s), and/or the object monitor, they may see a permission-related error message instead of successful evaluation. We strongly recommend storing monitors and their inputs in shared Projects.
中文翻译¶
错误参考¶
:::callout{theme="warning"} 对象监控器（Object Monitors）已被 自动化（Automate） 取代。自动化（Automate）是一款完全向后兼容的产品，为平台内所有业务自动化提供单一入口。 :::
本页面介绍使用对象监控器（Object Monitors）应用程序或对象资源管理器（Object Explorer）中的监控器（Monitors）视图时可能遇到的常见错误类别。
评估错误¶
监控器可能因底层数据问题而无法完成评估。监控器会自动重试，但某些错误可能需要手动干预。例如，如果被监控的对象类型被删除，则使用包含该类型对象的输入的监控器将无法完成评估。
监控器不同步¶
对象监控器（Object Monitors）使用对已保存探索（saved exploration）的引用来定义输入。此引用并非动态，而是根据监控器保存时探索的状态进行存储。如果探索发生更改，除非更新监控器，否则监控器将继续使用探索的旧状态进行评估。在这种情况下，监控器上会显示警告横幅：
通知效果错误¶
监控器评估成功后，通知可能无法发送。如果发生这种情况，历史事件将显示一个标签，表明该事件的通知未发送给订阅者，同时还会显示其他详细信息，例如错误标识符和错误消息。
操作效果错误¶
监控器评估成功后，操作效果（Action effects）可能无法执行。此失败可能由多种原因导致，包括操作逻辑发生更改，使其与监控器上保存的输入配置不兼容，或者未满足操作的提交条件（submission criteria）。如果发生此失败，历史事件时间线将显示一个标签，表明该事件的一个或多个操作未能执行，同时还会显示相关的错误详细信息。
权限¶
监控器评估使用各个订阅者的权限。这是为了确保监控器评估以及任何后续操作或通知效果始终反映用户在评估监控器时可能访问的数据。如果用户缺少查看输入对象类型、已保存探索和/或对象监控器的权限，他们可能会看到与权限相关的错误消息，而不是成功的评估结果。我们强烈建议将监控器及其输入存储在共享的项目（Projects）中。