FHR: How to monitor the status of the reindex from customer's side

This article will provide guidance on how to monitor the status of the data triggers. 

Scenario

The execution of data triggers can be monitored by checking the output status.

Steps

1. Identify your Fredhopper region (for example, eu1, us1, ap1, or ap2) and your environment name (for example, fas:test1).
2. Locate the data-id for the reindex job you want to check — this is the timestamp-based identifier from the trigger submission (for example, 2021-08-04_15-15-28).
3. Run the following curl command, substituting your region, environment, and data-id:

   curl -D - -k -u username:password -X GET \
   https://my.<region>.fredhopperservices.com/<environment>/trigger/load-data/<data-id>/status

4. Review the status code returned. Possible values are:

   Status	Description
   UNKNOWN	No known state yet — the trigger has not been picked up
   SCHEDULED	The trigger has been picked up and will start soon
   RUNNING	The triggered job is currently running
   DELAYED	The job is ready but delayed, for example due to insufficient capacity
   SUCCESS	The triggered job has finished successfully
   FAILURE	The triggered job has failed

5. If the status is FAILURE, refer to the Trigger Status Reference for next steps, or raise a ticket with the Support team.

Tip: Poll the status no more frequently than once every 60 seconds to avoid unnecessary load on the system.