Understanding the Automations Overview Table

  • Updated

The Automations table displays all Automations. To access this table, from the left navigation bar, go to Orchestration_N.png Orchestration > Automations. You can also go to Favorites to see your favorited Automations or My Automations to see Automations you created.

The table provides the following information:

  • Name: Name of the Automation you created or edited from the Details tab.
  • Member Type: Account or Person, Account indicates the Automation runs against accounts and Person indicates it runs against people.
  • Schedule: The schedule currently set for the Automation:
    • Scheduled: The Automation is scheduled to run in the future.
    • Single Run: The Automaton has a single run scheduled.
    • Recurring: The Automation is scheduled to run on a recurring schedule or ran previously on a recurring schedule.
    • No Schedule Defined: The Automation does not have a schedule set. The Schedule column is blank if no schedule has been defined.
  • State: Active or Inactive, Active means that the Automation is activated and will run at the scheduled date and time. Inactive means that the Automation has never run, was deactivated, or the Automation ran and won’t run again unless it is rescheduled and reactivated.
  • Job Status: Status of the most recent run:
    • Not yet run: The Automation has never run.
    • In progress: The Automation is currently running.
    • Succeeded: The Automation ran and the actions were successfully taken on all qualified accounts or people.
    • Failed: The Automation ran but the actions were not taken on the qualified accounts or people.
    • Partial Success: The Automation ran and the action was successfully taken on some of the qualified accounts or people or some of the actions were successfully taken on all or some of the qualified accounts or people.
    • Skipped: The Automation ran and the actions could not be taken on some of the qualified accounts or people. This means that some of the accounts or people that qualified based on the Selector criteria did not qualify for the actions. For example, the person you are trying to run the action against does not existing in the third-party platform you are performing the action in.
      After an Automation runs, the most recent run could contain multiple statuses (ex: Succeeded and Skipped members)
  • Created By: Owner
  • Favorite: Is the Automations Favorited
  • Created On: Date when the Automation was created
  • Last Updated On: Date when changes were last made to the Automation
  • Last Run: Date and time of last run

 

Was this article helpful?

0 out of 0 found this helpful