Logging package updates
- 최종 업데이트2026/04/16
Logging package updates
Review the updates in released versions of the Logging package such as new and enhanced features as well as fixes and limitations. The page also lists the release dates of each version, and the compatible Control Room and Bot Agent versions.
Versions summary
The following table lists the versions of Logging package released either with an Automation 360 release or as a package-only release (in descending order of release dates). Click the version link for information about updates in that package version.
| Version | Release date | Release type | Bot Agent version | Control Room build |
|---|---|---|---|---|
| 3.11.1 | 30 March 2026 | With Automation 360 v.40 (Sandbox) release | 22.140 or later | 45682 or later |
| 3.10.0 | 4 June 2025 |
Automation 360 v.37 (Sandbox) 릴리스(macOS 관련 지원) |
22.140 or later | 35124 or later |
| 3.8.0 | 6 September 2023 | With Automation 360 v.30 (Sandbox) release | 21.134 or later | 19321 or later |
- To download an individual package (updated in an Automation 360 release where you want only the package), use this URL:
https://aai-artifacts.my.automationanywhere.digital/packages/<package-file-name>-<version.number>.jar - For Log To File
package, the naming convention is:
bot-command-logtofile-<version.number>.jarFor example,
bot-command-logtofile-3.8.0.jar
For detailed steps on downloading a package and manually adding it to the Control Room, see packages에 Control Room 추가.
3.11.1
- Compatible Bot Agent version: 22.140 or later
- Compatible Control Room version: 45682 or later
| What's new |
|---|
|
Log to server action supported for Task Bot
The Log to server action is now available for Task Bots, allowing developers to write custom log messages directly within their automations. Developers can classify these logs by severity level (Informational, Warning, Error, or Critical) and include detailed descriptions and recommended remediation steps to support faster troubleshooting in production environments. See Log to Server action. You can view the automation runtime logs based on the storage location configured by the Control Room administrator. For example, if the administrator enables log forwarding to the Control Room, the custom log messages are recorded and stored in the Control Room repository. For more information on how to configure the default server location for storing automation logs, see Manage server location for storing automation logs - Cloud and Manage server location for storing automation logs - On-Premises. |
3.10.0
- Compatible Bot Agent version: 22.140 or later
- Compatible Control Room version: 35124 or later
| What's new |
|---|
|
The Log To File package is renamed as
Logging
The Log To File package is renamed as Logging . You can continue to access the actions within this package from the Logging option in the Actions menu. |
|
New action: Log to Server
Use the new Log to Server action to add custom logs within API Tasks. You can forward the custom logs along with the automation runtime logs to an external SIEM server. For more information about Log to Server, see Log to Server action. |
|
시민 개발자와 전문 자동화 전문가들은 이제 자신의 기기에서 macOS 플랫폼에서 자동화를 개발하고 실행할 수 있습니다. 이 package는 macOS를 지원하도록 향상되어, 일관된 개발 및 이식성 경험을 보장합니다. |
3.8.0
- Compatible Bot Agent version: 21.134 or later
- Compatible Control Room version: 19321 or later
| What's new |
|---|
|
Added new Log variables to file action
(Service Cloud case ID: 01263909) You can use the new, Log variables to file action in the Log To File package to log user-defined variable values of basic data types (such as Number, String, Boolean, and DateTime) to a log file. Use this action to troubleshoot and fix any automation issue by analyzing the variable values logged in the log file. Note: The
existing Log to file
action has been renamed to Log text to
file.
파일에 변수 기록 action 사용하기 | 변수 기록의 사용자 지정 선택 옵션을 파일 action에 사용하는 예 |
| What's changed |
|---|
|
bot 개발자용 지원 센터
|