Documentation Summary
Troubleshooting
Compatibility
Not applicable.
Limitations
The formula to calculate the seconds of delay takes into account all ordered documents, including the kit-documents. It ignores the data merge records.
Known Issues
Not applicable.
Logging
Each run of the submitted jobs check is recorded in the log file:
\WebPages\ROI360\Submitted Jobs Monitor\Log.txt
Each row of the log-file represents a single Design being rendered. The values are comma-separated, the log-file can be opened in a spreadsheet editor:
| Date and Time | Event Name | Delay | Order ID | Order External ID | Document ID | Document External ID | Status After Delay | Job Check Called |
|---|---|---|---|---|---|---|---|---|
| 2026-03-19 08:46:44 | OrderReadyToProduce_After | 30 seconds delay | 5531 | G-CB3BB528 | 6798 | D-697B751C | Rendered | yes |
| 2026-03-19 08:46:44 | OrderReadyToProduce_After | 30 seconds delay | 5531 | G-CB3BB528 | 6799 | D-697B751D | Submitted | yes |
The second field is the event-handler which had called the run.
If the Status inspected after the delay of any of the ordered Designs is either Submitted or ReadyToProduce, then the job-check is called. If all of the ordered Designs are Rendered, then the job-check is not called. The last field indicates whether the job-check was called or not.
Debugging
Not applicable.