Handling misfire event

An event may not be fired at the scheduled time due to multiple reasons. These are outlined as:

• No thread is available (refer to org.quartz .th readPool.threadCount property in the Administrator guide)
• System is busy

When the event is not fired at the scheduled time, it is considered as a delayed event. The delayed event is fired, when the thread becomes available or the system is not too busy. This delayed event is fired as long as delay is not more than misfire threshold. If delay is more than the misfire threshold, event is considered as a misfired event. The misfire threshold is specified by following parameter defined in quartz.properties file:

org.quartz.jobStore.misfireThreshold = 10000
10000 = 10 Seconds

10 seconds is the default value of misfire threshold, which can be changed, based on your requirements.
The process of changing the advanced properties of a File Event is explained below. 
 

To change the permission of an activity:

1. On the home page, expand Events tab in the left pane and then click File.
   
   
   
   

2. Under Action, click Morearrow and then click Edit  for the activity you want to edit. 

3. On the Edit File Event page, click to expand Advanced Properties on the bottom of the page.
   
   
   
   

4. In the Action on Misfire Event field, select the option Run Once to enable handling of misfire of the file event.
   

   The Run Once option will run only one collective instance of all the misfires for a particular event. The Ignore Misfire option will not run a misfired event.
    
   The default value for Action on Misfire Event field is set to Run Once for all of the earlier events.