Fileset / Payload Script Exit Code Status
Script Exit Codes
FileWave uses script exit codes to decide whether a Fileset should continue, retry, be skipped, or stop until an administrator takes action.
Quick answer: exit code 0 means success, 210 means the requirements check succeeded but the Fileset should be skipped, and 220 means the requirements check failed and FileWave should not retry automatically.
If a Fileset is skipped, missing from Kiosk, or blocked because a requirements script returned 210 or 220, use this table to confirm the expected behavior before troubleshooting the installer or activation scripts.
Status Value |
Status Description |
Severity |
Status Details |
|---|---|---|---|
| 220 | Failed! (Will Not Retry) | ERROR | Script exited with a failure, do not automatically retry |
| 210 | Success (Skipped Install) | ERROR | Script exited successfully, report Fileset as installed but skip actual installation |
| 0 | Success | OK | Script exited successfully |
| -1000 | Crashed | ERROR | Script crashed during execution |
| -1001 | Time Out Exceeded | ERROR | Script execution time took longer than Get Info > Executable > 'Wait for executable to finish' > 'Wait for:' |
| -1002 | No Logged In User | ERROR | Script could not run because no user is currently logged in |
| -1003 | Failed To Start | ERROR | Script could not run because the script failed to start |
Expected behavior
Requirements scripts processing rules
- If any requirements script returns 220, FileWave stops running scripts and stops trying to install the Fileset. No further action occurs unless an administrator manually requests it or a newer version of the Fileset becomes available. The Fileset status is reported as Requirements Not Met: Will Not Retry.
- If any requirements script returns a non-zero value other than 210, FileWave stops running scripts. Requirements scripts run again 2 minutes later.
- If a requirements script returns 210 and all other scripts return 0, the Fileset status is reported as Skipped. The Fileset is not installed.
- Only when all requirements scripts return 0 does FileWave install the Fileset.
Kiosk
If a requirements script returns 210 or 220, the Fileset is not available in Kiosk.
If a dependency Fileset has a requirements script that returns 210, it does not affect the availability of the main Fileset. If that dependency returns 220, the dependency fails and the main Fileset is not available in Kiosk.
Dependencies
- If the main Fileset is in the Skipped state, its dependencies are still processed and installed.
- If a dependency is in the Requirements Not Met: Will Not Retry state, that status does not propagate up the dependency tree. The main Fileset still fails because a requirement failed, but it is reported as a download, activation, or update failure for the dependency Fileset.
Other scripts
When a requirements script returns 210 or 220, the Fileset is not installed, so preflight, activation, and other later script types do not run. If the requirements scripts run again later and return values that allow installation, the other script types run as usual.
Inventory
- Filesets in Skipped status are reported to inventory as though they were installed.
- Filesets in Requirements Not Met: Will Not Retry status are not reported to inventory.
Common admin searches for this behavior include "Fileset skipped", "requirements script 210", "exit code 220 will not retry", and "why did my Fileset not appear in Kiosk".