...
Understanding Joget Deadline
| English |
|---|
Let's assume there are 100 pending instances where their deadline has matured. If the "System Settings > Process Deadline Checker Interval" is set to 1 hour, Joget will check and run each of the 100 pending instances in batches of 10. Once all 100 instances have been processed, it will then wait based on the Process Deadline Checker Interval, which in this case is 1 hour. And the cycle repeats itself. If the Joget server has many pending processes, the cycle time will be longer and may push the next cycle to start at a later time. |
| Warning | ||
|---|---|---|
| ||
Setting a short 1-second internal time may increase the CPU load and data IO in your Joget server, which may cause a performance hit. We would recommend an internal timer of 30 seconds or longer. |
...
The "List of Deadlines activated" menu will display the lists of pending instances and whether it has been executed or stopped.
The "Check" menu will display whether the deadline checker thread is running or stopped.
| Info | ||
|---|---|---|
| ||
The App is developed for MySQL/MariMariaDB. Should you use MSSQL, you will have to make necessary changes to the query in the "List of Deadlines activated" |
| Info | ||
|---|---|---|
| ||
If for some reason or other the deadline checker thread stops for some reason or other , you can:
|