View this page in the latest version of Appian. RPA 9.27 Hotfixes Share Share via LinkedIn Reddit Email Copy Link Print On This Page This page lists all resolved issues in Appian RPA version 9.27, as of the date indicated for each hotfix. Hotfixes for RPA 9.27 9.27.1-2c8ec15f52db (19 Nov 2026) ARPA-2418 - Critical The Open application and Close application actions no longer fail or hang on agents that run JDK 17The agent now starts with the Java option –add-opens=java.base/java.lang=ALL-UNNAMED, so the robot finds the correct window and process of the application that it starts. ARPA-2477 - Critical Queued executions are no longer cancelled in a chain after a robot disconnectsWhen a robot lost its connection without a normal sign-off, several queued executions for that robot could be cancelled with "Cancelled by CRON". Now only the interrupted execution is cancelled, and the other queued executions run as normal. ARPA-2386 - High Robotic task executions no longer fail while requesting dependencies after a cache failoverIn high availability environments, executions of robotic tasks with dependencies could intermittently fail in the Requesting Dependencies step after a failover of the internal cache service, with the error "Error during locked operation with lock id 'ARTIFACT_DEPENDENCIES…' (cause: RedisTimeoutException)". Executions now request their dependencies normally after a failover. jidoka-9.27.0-maint (23 Oct 2026) ARPA-2418 - Critical The Open application and Close application actions no longer fail or hang on agents that run JDK 17The agent now starts with the Java option –add-opens=java.base/java.lang=ALL-UNNAMED, so the robot finds the correct window and process of the application that it starts. ARPA-2477 - Critical Queued executions are no longer cancelled in a chain after a robot disconnectsWhen a robot lost its connection without a normal sign-off, several queued executions for that robot could be cancelled with "Cancelled by CRON". Now only the interrupted execution is cancelled, and the other queued executions run as normal. ARPA-2386 - High Robotic task executions no longer fail while requesting dependencies after a cache failoverIn high availability environments, executions of robotic tasks with dependencies could intermittently fail in the Requesting Dependencies step after a failover of the internal cache service, with the error "Error during locked operation with lock id 'ARTIFACT_DEPENDENCIES…' (cause: RedisTimeoutException)". Executions now request their dependencies normally after a failover. Feedback Was this page helpful? SHARE FEEDBACK Loading...