Program exit codes

Code 0

Program successfully completed.

Code 1

Incorrect function.
Indicates that the Action has attempted to execute an unrecognized command in the Windows command prompt cmd.exe.

Code 2

The system cannot find the file specified.
Indicates that the file cannot be found in the specified location. Most likely, the folder structure / path is configured correctly, however, the filename is either misspelled or the file is missing.

Code 3

The system cannot find the path specified.
Indicates that the specified path cannot be found.

Code 4

The system cannot open the file.
A path to the file is specified correctly, however, the user credentials do not contain the necessary permissions to the specified resource. Use the Run As feature to grant access to a local file or network path.

Code 5

Access is denied.
Indicates that the user has no access rights to the specified resource.

Code 259

0x103 · 103

The operation that was requested is pending completion. The process is still running.
The operation pending exit code 259 typically indicates that an application is still running and has not yet completed. However, custom applications may return any exit code, including the 259, as a custom termination status.

If your workflow relies on checking the running status of an application, and the application terminates with the code 259, it may result in an infinite loop waiting for a different exit code.

Code 9009

0x2331 · 2331 · 9,009

Program is not recognized as an internal or external command, operable program or batch file.
Indicates that command, application name, or path has been misspelled when configuring the Actions—Run CMD Command or Start App.

Code 2147942545

-2147024751 · 0x80070091 · 80070091 · 2,147,942,545

The directory is not empty.
The system attempted to delete a folder that was supposed to be empty, but it is not. Extremely rarely, the Remove Folder Action may experience this error when deleting folders within a path of about 32,000 characters deep. In a few seconds/minutes, Windows will enumerate files, and the problem will vanish upon retrying to remove the folder again.

Code 3221225477

-1073741819 · 0xC0000005 · C0000005 · 3,221,225,477

Access violation.
Indicates that the executed program has terminated abnormally or crashed.

Code 3221225495

-1073741801 · 0xC0000017 · C0000017 · 3,221,225,495

Not enough virtual memory is available.
Indicates that Windows has run out of memory. Observe Automation Workshop memory usage via the Operations Manager.

Code 3221225786

-1073741510 · 0xC000013A · C000013A · 3,221,225,786

The application terminated as a result of a CTRL+C.
Indicates that the application has been terminated either by the user's keyboard input CTRL+C, or CTRL+Break, or by closing the command prompt window.

Additionally, Windows Server 2025 exhibits a behavior where CMD commands and console applications, when launched under the new Windows Terminal instead of the legacy Windows Console Host, may encounter issues if started in rapid succession.

Due to a known bug, the terminal windows can become unresponsive, and after a certain number of these hung terminals accumulate, Windows automatically terminates them. This occurs without any user interaction—no CTRL+C or CTRL+Break input—yet the affected console applications exit with code 3221225786 (0xC000013A), potentially leading to confusion during diagnostics, as the exit code typically indicates an intentional user-initiated interruption.

Code 3221225794

-1073741502 · 0xC0000142 · C0000142 · 3,221,225,794

The application failed to initialize properly.
Usually, for interactive apps, a user with administrator rights is required. Moreover, the user must log on at least once to allow Windows to prepare the Windows Station and Desktop.

This error also may indicate that the application has been launched on a Desktop to which the current user has no access rights. Another less likely cause is that either gdi32.dll or user32.dll has failed to initialize.

Code 3221226505

-1073740791 · 0xC0000409 · C0000409 · 3,221,226,505

Stack buffer overflow / overrun.
This error can indicate a bug in the executed software that causes a stack overflow, leading to abnormal termination of the software.

Code 3221225725

-1073741571 · 0xC00000FD · C00000FD · 3,221,225,725

Stack overflow / exhaustion.
This error can indicate a bug in the executed software that causes a stack overflow, leading to abnormal termination of the software.

Code 3762507597

-532459699 · 0xE0434F4D · E0434F4D · 3,762,507,597

Unhandled exception in .NET application.
More details may be available in the Windows Event Log.

Code X

User-defined custom exit code.
Applications can return any predefined and custom codes, if they are programmed to do so. Additionally, Automation Workshop allows terminating apps directly from automated workflows providing any exit code. Valid value range: 0 through 4,294,967,295. The Terminate App Action supports a very flexible syntax for exit codes, for example:

• 3221225786 · a regular integer that is popular in batch programming.
• 3,221,225,786 · a number where thousands are comma-separated for easier readability.
• 0xC000013A · hexadecimal exit code, commonly used in Windows applications and log files.