Deciding when to Abandon / Re-run or Resume a failed CIM job

Customer Interaction Manager, Real-Time Interaction Manager, TD Channel Integration Services
Teradata Employee

Deciding when to Abandon / Re-run or Resume a failed CIM job

Deciding when to Abandon / Re-run or Resume a failed CIM job

Teradata Employee

Re: Deciding when to Abandon / Re-run or Resume a failed CIM job

One has two courses of action when addressing a failed group batch job: Abandon the job or Resume it.  The Abandon and Resume actions of Job Status Dashboard allow CIM users to apply the corresponding action.  For futher information on the Job Status Dashboard, refer to Chapter 4 of the CIM Object Processing guide.  

Generally speaking, CIM users are aware of these functions but may not be sure when to apply one versus the other.  In some cases, one may be tempted to use the action that may be the most convenient or fastest.  For example, one may have a job that has failed due to a lock timeout.  Often, a lock timeout occurs because some other job has failed and is holding a lock on a CIM object that's needed by the current job (see KCS article KCS004659 for more information about lock timeouts).   Once the other failed job has been addressed, the choice of abandoning the current job is easy because the job never initiated any real work because it never acquired a lock.   Therefore, there are no consequences for abandoning the job as there is no work to be lost.


However if the job fails after completing one or more phases of processing, one should always first consider resuming the job.  When deciding on whether to abandon a job, consider the affect on future job runs:

  • Is the job being abandoned so that the it can be run again from the beginning (start over)?  If so, be sure that the abandoned run has not produced any outputs.  If it has produced outputs, running it again can lead to duplication of output data.  One should take action to avoid duplicates by excluding the leads that were successfully output during the abandoned run.
  • Is the job a group job? Does it include multistep communications?  If so, be sure to consider any responses, timeouts or events that have been applied during the run.  The application processes new responses and timeouts during the Apply Responses and Cycle Leads processing phases.    These phases can apply changes to active leads based on responses or timeout data .   This, in turn, can make the leads eligible for output.  Note that the leads are only eligible for output during the CURRENT job run and cannot be output by another job run.  The resulting loss of the outputs can affect the communication's results / effectiveness.   
  • Did the job generate and publish any new leads before it failed?  If so, these leads can affect function such as deduplication and recency so consider the impact of these leads on future processing and make appropriate adjustments.

For additional assistance on determining the impact of abandoning a failed job, contact CIM support.