|The capabilities described on this page are included in Appian's standard capability tier. Usage limits may apply.
Under the Monitoring tab, you can manage actions and events in the Appian RPA console.
Actions are operational steps the console can take when certain criteria are met, using Events as the trigger. For example, you can configure the console to send an email to a person or group of people when a robotic task begins or ends.
To create a new action:
Events are used to launch actions, but they are also logged in the console so administrators have a comprehensive view of what actions occur and when.
The following table described each event that can be triggered within the console:
|The FILE API is called. This method isn't recommended because it was developed specifically for legacy systems not supporting REST API. It is strongly recommended to use the REST API whenever is possible.
|The main methods of the console's REST API are invoked.
|The backup process of the console ends.
|The backup process of the console starts.
|A remote control command is received, either activating the microphone in the browser (only for Chrome) or using the mobile application.
|The console is started.
|The free disk space is under the threshold defined for the console in Settings > Configuration.
|An execution is self-removed after it ends.
|The execution of robotic tasks is disabled on the console.
|The execution of robotic tasks is enabled on the console.
|A user asks for an email to reset credentials.
|A user logs into the console.
|A login attempt to the console is unsuccessful.
|A user logs out of the console.
|A container is started.
|A container is stopped.
|A robot is disabled.
|A robot is enabled. It occurs when it connects to the console and shows as Enabled.
|A robot has reached its maximum specified memory.
|A robot is locked (a user needs to log in).
|The free disk space for the robot is under the threshold defined in Robot detail page.
|The console detects that a robot has gone offline.
|A specific agent instance is successfully registered. The agent is started on a robot and connects to the console.
|A robot has been unlocked.
|A report was generated and is available for download.
|A robotic task execution is aborted.
|A robotic task ends its execution.
|This event is specifically triggered by the robots through the platform API. It allows you to monitor specific situations notified by the robots to the platform.
|An attempt was made to run a robotic task whose execution is disabled on setup, or that is out of its execution schedule.
|A robotic task is queued for execution.
|An execution has been queued for more than a specific amount of time without being executed.
|A robotic task starts its execution.
|This event is generated at a specific configured time, being able to associate any action.
Manage Actions and Events