Specifications
• The job has an invalid file format causing a third-party application to issue a fatal error
message.
• The job matches none of the file filters set on the outgoing connections of a particular folder.
Switch offers a number of facilities for handling problem jobs, from detecting their presence to
re-injecting them in the flow after the problem has been resolved.
Detecting problem jobs
There are various ways to detect the existence of problem jobs in Switch:
• The Problem alerts user preferences allow specifying that a notification email should be sent
to the system administrator when a job is moved to the problems folder.
• The Problem jobs flow element can be placed on the canvas right inside a flow design; its
icon displays a red error mark when there are problem jobs present (see Viewing an active
flow on page 103).
• The Dashboard pane displays an overview of the current problem jobs at any given time. See
Viewing flow problems on page 111.
Researching problem jobs
Switch assists with locating and researching problem jobs in various ways:
• When you select the Problem jobs flow element in the canvas; the Files pane displays a list
of the problem jobs (for this flow or for all flows depending on how the Problem jobs flow
element is configured).
• The context menu for the Dashboard pane provides options to locate the flow element causing
the problem in the canvas, and to show the problem job in the Files pane. See Viewing flow
problems on page 111.
• The Messages pane shows all messages issued by Switch and the processes under its control;
use the pane's filtering capabilities to pinpoint the messages issued for the problem job or
by the process(es) involved in the problem; this may provide some context in case the problem
was really caused by an occurrence further upstream. See Viewing log messages on page 107.
Retrying problem jobs
When Switch moves a job to the Problem jobs folder, it remembers the original location of the
job in its internal job ticket. This makes it possible to move the job back to the location where
it left the flow for another attempt at successful processing, without loosing any of the job's
history (which is also stored in the internal job ticket). The process of moving the job back in the
flow is called retrying the job.
It is meaningful to retry a job only after you have fixed the problem (or at least believe you did)
by reconfiguring a process, adjusting the flow design, or tweaking the job itself.
Note:
Leave the job in the Problem jobs folder and leave its file name intact (including unique name
prefix and file name extension); if you change the location or the file name Switch may loose
the connection with the job's internal job ticket and it can no longer retry the job.
115
Enfocus Switch 10