Skip to main content

Fileset / Payload Script Exit Code Status

Script Exit Codes

FileWave

Whenuses script exit codes to decide whether a scriptFileset runs,should onecontinue, ofretry, be skipped, or stop until an administrator takes action.

Quick answer: exit code 0 means success, 210 means the belowrequirements errorscheck maysucceeded but the Fileset should be skipped, and 220 means the outcome.requirements

check

failed
and
FileWave should not retry automatically.
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 filesetFileset 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 failurethe script failed to start the script

Expected behavior

Requirements scripts processing rules

  • If any of the requirements scriptsscript returns 220,220, weFileWave stopstops executingrunning scripts and also stopstops trying to install the fileset.Fileset. No further action will be done,occurs unless an administrator manually requestedrequests by an administrator,it or unless a newer version of the filesetFileset isbecomes available. The filesetFileset status will beis reported as "Requirements Not Met: Will Not Retry"Retry.
  • If any ofrequirements the scriptsscript returns a non-zero andvalue ≠210,other wethan stop210, executingFileWave stops running scripts. RequirementRequirements scripts will be executedrun again 2 minutes later.
  • If anya ofrequirements the scriptsscript returns 210 whenand all other scripts return 0,0, the filesetFileset status will beis reported as "Skipped"Skipped. The filesetFileset willis not be installed.
  • Only ifwhen all requirements scripts return 0,0 thendoes we willFileWave install the fileset.Fileset.

Kiosk

If a requirements script returns 210 or 220,220, the filesetFileset willis not be available in Kiosk.

If thea dependency of a filesetFileset has a requirements script that returns 210,210, it willdoes not affect the availability of the main fileset.Fileset. However,If ifthat itdependency returns 220,220, the dependenciesdependency willfails fail soand the main filesetFileset willis not be available in Kiosk.

Dependencies

  • If the main filesetFileset is atin "Skipped"the Skipped state, its dependencies willare still be processed and installed.
  • If a dependency is atin "the Requirements Not Met: Will Not Retry",Retry state, that status does not propagate up the dependency tree. This means the installation of theThe main fileset willFileset still failfails duebecause toa failedrequirement requirements,failed, but theit main fileset will simply beis reported as Download/Activation/Updatea ofdownload, activation, or update failure for the dependency fileset failure.Fileset.

Other scripts

WheneverWhen a requirements script returns 210 or 220,220, the filesetFileset doesis not get installed, so other types of scripts (preflight, activation, etc)and willother later script types do not berun. executed. Only in caseIf the requirements scripts are run again later and theyreturn change,values thenthat allow installation, the fileset might get installed and in that case other script types of scripts will get run as usual.

Inventory

  • Filesets in "Skipped"Skipped status are reported to inventory,inventory likeas ifthough they were actually installed.
  • Filesets in "Requirements Not Met: Will Not Retry"Retry status are not reported to inventory at all.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".

Back to top