This topic provides the systematic instructions to resolve the scenario where the OBCL EOD job has failed and the OBSCF EOD job has run successfully.

1. Recommended approach
   1. Restore the database backup.
   2. Run the OBCL EOD job first.
   3. After the successful completion of the OBCL EOD batch, run the OBSCF EOD job.
2. Alternate approach

   Follow the below approach if there is no database backup.

   Note:

   It is important to exercise caution when implementing this approach as it may not work in all scenarios, such as when the finance maturity is on the said date, or when the finance has been marked as Non-Performing Asset (NPA), etc.,
   1. In the SCF_BATCH_STATUS table, delete all the entries for that system date and next day.
   2. Delete entry for MARK_TI and RELEASE_CUTOFF event.
   3. In CMC_TM_SYSTEM_DATES and CM_TW_SYSTEM_DATES, change the system date to the previous date.
   4. From the CM_TM_BRANCHEOD_INSTANCES table, copy the Workflow ID.
   5. Delete the Workflow ID from the WORKFLOW table.
   6. Then delete the entry from CM_TM_BRANCHEOD_INSTANCES for that system date.
   7. Reach out to OBCL to resolve the OBCL EOD job failure.
   8. After the successful completion of the OBCL EOD batch, run the OBSCF EOD job.