When a back-end system needs maintenance or is becoming unresponsive, you might want to suspend document retrieval for triggers that interact with the back-end system. By suspending document retrieval, documents that would normally accumulate on Integration Server awaiting processing remain on the messaging provider. This keeps memory and other server resources available for other activities. When the back-end system becomes available, you can resume document retrieval for the associated triggers.

After suspending document retrieval for all triggers, you might resume document retrieval for specific triggers. If Integration Server is functioning under an unusually heavy load, you might first suspend retrieval for all triggers and then gradually resume retrieval, starting with the triggers involved in key processes.

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