Resource management

The Resources - Management screen allows you to retire and un-retire runtime resources, as well as configure their diagnostics settings.

Retire a resource

To retire a resource that you do not want to be used anymore, either permanently or temporarily, double-click the resource, or drag it into the Retired Resources panel. You can also select multiple resources and drag them into the Retired Resources panel at the same time.

To retire groups of resources, select the group and drag it into the Retired Resources panel. All resources within the group will be move but the folders in which the resources were previously located will be retained as empty folders.

To un-retire a resource, drag it into a folder in the Active Resources panel.


By right-clicking any number of active resource PC and choosing Logging Level from the menu, you can configure diagnostics options for those resource PCs. The available options are:

  • Log Overriding – usually this is set to 'Default', and logging by processes running on the resource PC is inhibited according to the process design (see Stage Logging). However, occasionally it may be useful to override this log inhibiting and have additional logging. By selecting 'All stages', any log inhibiting defined in a process is ignored and all stages are logged. This will result in very verbose logs, but may be useful in diagnosing problems. An intermediate option, 'Key stages', is also available – this overrides only on stages such as Code Stages, Navigate, Read, Write, Wait and Action/Subprocess calls.
  • Log Memory Statistics – if enabled, all process log entries are accompanied by a record of how much memory (Working Set) was in use by the main Blue Prism executable at the time. Additionally, if the logged action refers to a target application, the identity and memory usage of that target application is also recorded.
  • Include Memory Cleanup – enabling this may produce more useful figures when diagnosing suspected memory leak issues.
  • Log Web Service Communication – enabling this causes low-level web service communication to be logged – specifically, SOAP messages are logged in full detail. For consumed web services, the information is logged as part of the corresponding session log. For exposed web services, it is logged in the event log for the relevant resource PC.

If a resource PC is online when its diagnostics settings are changed, it does not need to be restarted for the new settings to take effect. It will pick up and begin using the modified settings within two minutes at the most.

Reset FQDN

By right-clicking any number of active resource PCs and choosing 'Reset FQDN' the recorded FQDN for those resources can be reset. See the registration settings for more details. This option is only available when in 'Register using machine (short) name, communicate using FQDN' mode.


The following permissions can be used to control what particular users can do with resources within the Resource Management tab and Control Room. Refer to User Permissions for more information about how permissions are assigned to users through User Roles.



View Resource

Allows the user to see resource in relevant tree view, including sessions running processes that the user has access to etc. Also allows some queries to be made via the telnet/HTTP interface.

Configure Resource

Allows the user to change logging options, reset FQDN, retire/un-retire etc. Provides access to manage resources tab under System. View permission is also implied.

Authenticate as Resource

Allows the user account to be used for runtime authentication when starting up a resource.

View Resource Screen Capture

Allows the user to view exception screenshots assuming they have access to control room.

Control Resource

Allows the user to create a session on the resource, and fully interact with it via the telnet/HTTP interface. View permission is also implied.