When a back-end system becomes unresponsive or requires maintenance, you might want to suspend document processing for triggers that interact with that back-end system. If the back-end system is not available because of maintenance or failure, trigger services that interact with the system would probably not execute successfully. Suspending document processing for the associated triggers allows for more effective resource utilization because you keep resources that would have been used for unsuccessful document processing available for other tasks.

After suspending document processing for all triggers, you might resume document processing for specific triggers. If Integration Server is operating under a heavy load, you might first suspend all document processing and then gradually resume document processing, starting with the triggers involved in critical processes.

If Integration Server suspends document processing for a serial trigger because the associated trigger service ends in error, you need to resume document processing for the trigger. For more information about configuring a serial trigger to suspend retrieval and processing automatically after an error, see webMethods Service Development Help.