Configure the Run-time Settings Tab

On the Run-time Settings tab of the robotic task configuration, you can configure the following settings:

• Execution settings
• Simultaneous executions
• Scheduling and availability window
• Automatic Process Clean-Up

Execution settings

In this section, you can choose how this robotic task behaves when executions are launched consecutively from an Appian process model. Options include:

• Run setup and cleanup for each execution: Each consecutive robotic task execution includes the actions specified in the setup and Cleanup sections.
• Skip setup and cleanup for consecutive executions: Setup actions only occur at the start of the first execution, and cleanup actions only occur at the end of the final execution.

If the robotic task doesn't require a robot to be reset before the next execution occurs, you can choose Skip setup and cleanup for consecutive executions. This option speeds up each execution, and the compounded time savings can make the overall set of consecutive executions much faster.

Learn more about the Setup and Cleanup sections.

In some scenarios, Setup and Cleanup sections are still run even if you choose to skip them for consecutive executions. These sections run when the:

• Next execution is for a different robotic task
• Execution runs into an unexpected exception
• Robot does not have any further pending executions to pick up

Certain components of the robotic task configuration may behave differently when setup and cleanup are skipped:

• Variables: When setup and cleanup are skipped, any robotic task variable that isn't a parameter is reset to the value it had at the end of the last setup. Any robotic task variable that is a parameter will be set to the value defined as part of the execution request. When you choose to skip setup and cleanup, avoid updating any variables used in the Setup section.
• Credentials: If you use credentials in a Setup section, the credentials are reserved and won't be released until the Cleanup section successfully completes. This means that if the robotic task executes consecutively and the configuration is set to Skip setup and cleanup, then the credentials won't be released until the final execution's Cleanup section completes. Credentials used in the main section are released at the end of that specific execution.

Simultaneous executions

This setting controls the maximum number of robotic task executions that can run at the same time, including both enqueued and running executions. This helps manage resource allocation and prevents system overload.

• Maximum simultaneous executions: Set the maximum number of executions that can be active simultaneously for this robotic task.
• Queue management: When the limit is reached, additional execution requests are queued until an execution slot becomes available.

This setting is particularly important when:

• Your robotic task processes high volumes of requests.
• System resources need to be carefully managed.
• You want to prevent conflicts between multiple instances of the same task.

Scheduling and availability window

Configure when your robotic task is allowed to execute by setting up scheduling rules and availability windows. This feature allows you to:

• Schedule recurring executions: Set up automatic execution at specific times.
• Define availability windows: Restrict execution to specific days of the week and time ranges.
• Manage resource usage: Ensure robotic tasks run during optimal system performance periods.

Scheduling options include:

• Daily, weekly, or monthly patterns: Configure regular execution schedules.
• Time-based restrictions: Limit executions to business hours or maintenance windows.
• Day-specific rules: Allow or restrict execution on particular days of the week.

Example scheduling scenarios:

• Run data processing tasks only during off-peak hours (nights and weekends).
• Execute report generation every weekday at 9:00 AM.
• Restrict system maintenance tasks to specific maintenance windows.

Automatic Process Clean-Up

Every robotic task execution creates metadata or artifacts to help you evaluate how it performed. Over time, this data accumulates and can consume disk space to the point of negatively impacting performance. To keep your environment performing its best, you can configure when to delete this information. If you need certain information for auditing purposes, we recommend maintaining an Appian database table with the information you might need, such as the item processed, status of the process, and duration.

• Delete completed or cancelled executions including artifacts (days): Number of days after which robotic task executions (including artifacts) are removed in order to free disk space. The execution data is removed altogether, so it won't appear in the list of executions.
• Delete only artifacts (days): Number of days after which artifacts generated by executions are removed in order to free disk space. The list of artifacts affected by this option are inbound (parameterized robotic task variables), images, files of results, and video.

Feedback