By default, device extensions like Histories, Schedules, and others contain a “Retry Trigger”-named component, appearing in the Nav tree but not in any Manager view (Figure 46).

Retry Trigger is unique in that it requires no linking of its output for operation.

Upon any unsuccessful execution of a descriptor component (i.e. history import descriptor, schedule import descriptor, and so on) contained in that same device extension, the Retry Trigger defines subsequent “retries” that will automatically occur upon the interval period defined (default value is 15 minutes). This continues until successful execution occurs.