Reviewing the historical automation and modifications implemented by xFanatical Foresight is essential for diagnosing rule setup issues and conducting audits. xFanatical Foresight maintains a comprehensive log of all automations, allowing you to understand which tasks were automated, their timing, and the outcomes achieved. 

xFanatical Foresight Rule logs, including time, rule name, used actions, successful actions and failed actions. Each row is a rule execution.
xFanatical Foresight Rule Logs

Instructions

Follow these steps to access the rule logs.

  1. Sign into xFanatical Foresight
  2. Go to the Logs page.
  3. Find the rule logs displayed in a table. Each row represents a rule execution.
  4. Click chevron icon right in each row to expand the rule log details.

Log Details

Rule Log Stats

The log stats show important statistical information about the rule execution. If xFanatical Foresight automated the actions successfully in the rule execution, reaching till the end of the workflow, then the rule execution overall outcome is successful, displayed as a green light Green light used in xFanatical Foresight. Otherwise, if xFanatical Foresight quitted the workflow early without completing the actions in the workflow due to errors, then the overall outcome is a failure, displayed as a red light Red light used in xFanatical Foresight. 

Rule Log Stats in xFanatical Foresight, including rule name, start and end time, duration, used actions, successful actions, failed actions, total actions and skipped actions. The result of the successful rule execution is displayed as a green light.
Rule Log Stats in xFanatical Foresight

Terminologies

  • Timestamp. The time when the rule execution happened. 
  • Rule. The rule name when the rule execution happened. It may not be the same as the latest configured rule name.
  • Used Actions. The number of actions counted toward the monthly action quota.
  • Successful Actions. The number of actions with a successful result. For example, a result of the Suspend user action is having a given Google Workspace user suspended, then this action is considered successful. 
  • Failed Actions. The number of actions with a failed result. For example, the Suspend user action does not suspend the given user as expected, because the Google Workspace user didn't exist. Then this action is considered failed. 
  • Total Actions. The total number of actions in the rule when the rule execution happened. It may not be not equal to the number of actions in your current rule configuration if you have edited the rule since then. 
  • Skipped Actions. The number of actions xFanatical Foresight didn't automate. Assuming you have a 7-steps rule, xFanatical Foresight automated the first 4 actions, but the 4th action failed due to a data error. Then the rest 3 actions are skipped. The rule execution ends early. 
  • Start Time. The time when the rule execution started. 
  • Finish Time. The time when the rule execution completed or quitted. 
  • Duration. The duration in seconds of the rule execution. 

Rule History

The rule history card shows the trigger event and the action history. The trigger event describes what triggered the rule, e.g. someone sent you a calendar event invite. The action history lists the tasks xFanatical Foresight has automated, either some or all of the rule's actions.

Each entry shows a status light:

  • A green light means the trigger or action ran successfully.
  • A red light means it failed. The log includes a failure reason, e.g. the given user is not found, or the email recipient cannot be empty. These reasons help you troubleshoot your rule configuration or unmet conditions.

Actor chip support

Starting with v5.0.0, a trigger or action can run on behalf of another user in your organization through a service account. In that case, an actor chip appears before the history message to show whose account was used:

  • Grey chip with avatar, name and email: xFanatical Foresight acted as the selected user successfully.
  • Red chip with avatar and email: xFanatical Foresight could not act as the selected user.
  • Hover over the chip to see a tooltip explaining whether acting as that user worked, and if not, why.

The actor chip only tells you whether xFanatical Foresight could act as the selected user. The trigger or action itself can still fail for other reasons. For example, a Create Gmail label action fails if the label text color is not one Gmail supports, even when the chip shows success. Always check the status light and failure reason too.

A rule history can contain a mix of entries with and without an actor chip. No chip means the trigger or action ran as you, the signed-in user.

A rule history can contain a mix of entries with and without an actor chip