This page explains the status codes for monitoring trigger execution.
Introduction
When using triggers in the managed services environment a job will be executed for the trigger. While the job is executing its status can be monitored using the REST API or the status file File API.
The status file has a very simple format: the first line contains a machine-readable status code, and all following lines contain additional information intended for humans.
For example a "success" usually looks like:
SUCCESS
A typical "failure" looks like:
FAILURE com.fredhopper.controller.data.DataHelper$ChecksumException: Cannot find checksum for data.zip in checksum file, available checksums are [ata.zip] This may indicate that the upload of data.zip was not successful. Please re-generate the checksum, upload the files, and trigger the data loading again.
While a job is running the information in the file may change, and typically this looks like this:
RUNNING Execution started at ...
Reference
| Status | Description |
|---|---|
| UNKNOWN | No known state yet: trigger has not been picked up yet |
| SCHEDULED | Trigger has been picked up, and will start execution soon |
| RUNNING | Triggered job is currently running |
| DELAYED | Triggered job is ready to run, but delayed (for example due to insufficient capacity) |
| SUCCESS | Triggered job has finished successfully |
| FAILURE | Triggered job has failed |
Comments
0 comments
Article is closed for comments.