1.16.1 Timing of JP1 event reporting

You can use JP1/IM to centrally monitor the JP1 events issued by JP1/AO. The following table describes the timing with which JP1/AO issues JP1 events.

Table 1‒25: Timing of JP1 event notification

Timing		Event ID
Category	Subcategory
Task status detected#1	A task enters Waiting for Response status#2	0x00007000
	A task enters Completed status
	A task enters failed status
	A task enters Canceled status
JP1/AO operating status	JP1/AO starts	0x00007010
	JP1/AO shuts down
Error detected in task processing engine	An error occurs when you execute a task processing engine command.	0x00007020
Error detected in database#3	An error occurs when attempting to connect to the database	0x00007030

#1

JP1/AO monitors the status of tasks at regular intervals (once every 30 seconds by default). The JP1 event is generated when JP1/AO detects the change, not when the change itself occurs. JP1/AO will not issue additional events until the status changes again.

#2

If a task transitions to the waiting for response status and the user enters a response in less than 30 seconds in the Respond dialog box, the JP1 event reporting the change to the waiting for response status might not be issued because the task has already transitioned to another status.

#3

JP1 events resulting from the same occurrence will not be issued for the next hour after the first notification.

Tip

If there are too many events generated by the task processing engine and it becomes difficult to identify events issued by JP1/AO, filter the events in the JP1/IM interface.

To Page Top