Skip to content

Configure Local Client Settings

Local Settings primarily stores client configuration specific to the current device. System startup, close behavior, zoom, memory limits, cache directory, and system logs appear only in the desktop client. RPA task settings also apply to local task execution.

Common Settings and RPA Tasks

Local common and RPA settings
Local common and RPA settings
No.FeatureDescription
1Launch at startupControls whether the application starts with the operating system; uses the current operating system's startup capability
2When closing the applicationSelect Ask, Minimize, or Quit to determine what closing the main window does
3ZoomSets the client main window's zoom percentage from 50 to 200; changes apply immediately and are saved automatically. Use Ctrl/⌘ + + to zoom in, Ctrl/⌘ + - to zoom out, or Ctrl/⌘ + 0 to reset to 100%
4Memory limitStops opening new browser windows when system memory usage reaches the threshold; accepts an integer from 1 to 100 percent
5Concurrent tasksMaximum number of legacy RPA and RPA Plus tasks that can run on the current device
6Automatically delete task logsRemoves RPA task logs older than the retention period each day
7Log retentionAvailable when automatic deletion is enabled; accepts 1-30 days

Choose task concurrency based on CPU, memory, and target page load. Excessive concurrency can cause profile launch failures, slow page responses, or resource contention between tasks.

Browser Cache and System Logs

Local cache and log settings
Local cache and log settings
No.FeatureDescription
1Cache directoryDisplays the root directory for browser profile cache on the current device
2ViewOpens the folder containing the current cache files
3ChangeSelects a new directory after a migration warning; existing cache files are not moved automatically
4Automatically delete cacheEnter 1-30 days to remove cache for profiles not used within that period; leave empty to disable
5Scan and Delete NowScans for eligible cache and displays the count and estimated space before confirmation
6Scan and confirmationDisplays scan failures, running profiles that will be skipped, and estimated space; confirmed deletion cannot be undone
7System LogsOpens the client system log directory for troubleshooting

Change the Cache Directory

  1. Click Change and read the migration instructions.
  2. Confirm that you understand, open the current directory, and select a new path.
  3. Move existing cache files to the new directory manually.
  4. Return to the client and click Save Settings.

You cannot run Scan and Delete Now while a cache directory change is unsaved. Running profiles are skipped during cleanup. Confirm that the remaining profile cache is no longer needed before deleting it.

WARNING

Cache deletion cannot be undone. Do not use Scan and Delete Now for profiles that still require local data or login sessions, and do not omit the manual migration step when changing directories.