---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/conversational-interfaces

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Manage Proactive Triggers

# Manage Proactive Triggers {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

After admins have installed Proactive Triggers and created related actions and rules, admins can check that the Proactive Triggers feature is performing as expected. For example, admins can view the Proactive Execution History table and the Proactive Daily Report table.

This topic includes information admins can use to see if the Proactive Triggers feature is performing as expected. For example, admins can review the Proactive Triggers history tables to make sure that the rules and actions are working as intended.

This topic also includes common issues that admins may encounter when they're creating rules and actions, along with the proposed solutions.

## View Proactive Triggers history and report tables {#manage-proactive-triggers-2__section_cpd_hpz_dwb}

To see if the Proactive Triggers feature is running as intended, admins can review these two tables' data:

* Proactive Execution History  (sys_cs_ptrigger_execution) table
  * Real-time execution history of Proactive Triggers events.  
    Dica:  
    The Notes column provides a brief rule execution status. For additional information about why Proactive Triggers didn't run successfully, select the execution event from the Created column, and then view the Details field under the Others section.
  * The data from this table is removed every seven days.
  {#manage-proactive-triggers-2__ul_hmv_p53_fwb}
* Proactive Daily Report (sys_cs_ptrigger_report_daily) table
  * Aggregated execution data by user, rule, and action per day.
  * Execution data is processed every hour and updates this table.
  * The data from this table is removed every 35 days.
  {#manage-proactive-triggers-2__ul_urm_4rz_dwb}
{#manage-proactive-triggers-2__ul_jgk_qqz_dwb}

## Common issues and resolutions {#manage-proactive-triggers-2__section_d14_hp5_2wb}

The following table lists issues that you may encounter when you're creating rules and actions, and the suggested resolutions.{#manage-proactive-triggers-2__table_dd3_511_2wb__entry__2}

| Issue | Resolution |
|-|-|
| If a trigger type is defined as a URL in the rule, when the page is actually a catalog item, knowledge, or portal, the rule won't run. | Admin must fix the rule to match the page type. |
| The Frequency is set to run once per user but the rules don't run. | Clear the rule history at the rule level. For details on clearing the rule history, see [Multiple Proactive Triggers rules and actions](https://servicenow-prod.fluidtopics.net/E_q6lGOxEzmi7bKiD3HmWA "The Proactive Triggers feature uses rules and actions to trigger context-specific Virtual Agent conversations with end users on the web client."). |
| Rule doesn't run for some end users, and the action type selected is virtual agent topic. | End users may not have access to the Virtual Agent topic defined on the action. Check the access to the topic in Virtual Agent Designer. |
| The Proactive Triggers rule doesn't run. | Close any active conversations in the Virtual Agent chat widget. |
[ ]

{#manage-proactive-triggers-2__table_dd3_511_2wb}