Debugging delayed triggers

Debugging delayed triggers is challenging because there is no one around when they run. See Delayed and recursive triggers for information about delayed triggers.

The following considerations should be helpful for debugging delayed triggers:

1. Always debug triggers using the trigger debugger before configuring the delay criteria. See Debugging complex triggers for details.
2. Check the trigger queue page by clicking Queue on a record view page to see when the trigger is scheduled to run.
3. Remember that Object Script on delayed triggers uses the Server API role to calculate permissions. For information on permissions and access control, see Access control.
4. Infinite Blue recommends using Create Audit Trail Record triggers for debugging purposes, because the regular debug window is not available for delayed triggers.