WPs abort with exit code='255' when the Password Vault of an existing Login object is changed from Automation Engine to CyberArk while active Events are running.
search cancel

WPs abort with exit code='255' when the Password Vault of an existing Login object is changed from Automation Engine to CyberArk while active Events are running.

book

Article ID: 439534

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine Automic SaaS Automic Automation CA Automic One Automation

Issue/Introduction

A complete Automation Engine system outage occurred in which all Work Processes (WPs) aborted simultaneously with exit code 255.

The issue was observed after the Password Vault configuration of an existing Login object was changed from Automation Engine to CyberArk while the Login object was actively being referenced by running Event objects.

Environment

Release: 24.4.x 

Component: Automation Engine (Hosted on Linux only)

Note: Issue does not occur in Windows Environment

Cause

DE192229

Resolution

Update to a fix version listed below or a newer version if available.

Fix version:

Component(s):  Automation Engine

Automation Engine 24.4.5 - Planned release July '2026

Additional Information

Desc: A problem has been fixed that caused the Work Process to crash when a Login object was switched from AE to CyberArk during a running event.

Note: This Knowledge Base article will be updated as additional findings, fixes, or recommendations become available. Subscribe to this article to receive notifications on future updates related to this issue.