Cancel Pending - TES 6.1.0

Question

Has anyone worked with trying to apply the status of Cancel Pending with TES 6.1.0?
We have a process that goes out to a third party API to check for for files.
The API will come back with -1 when no files are available.
We have a need that if file "a" is available it is to be processed first before file "b".
If file "a" is not available we can then go ahead and process file "b".
We created an event on the process that checks for files for file "a"  accessing the api of our third party vendor to cancel
pending when it had a status of -1.   Our thought process being that the job depending on file "a" would
then be released to run. 
However, when we run this scenario - Tidal would change the status of the first job to cancel pending and then within a
split second change the status to completed abnormally.  The successor job would not run as the previous
job has a status of completed abnormally.

Answer 1

This forum is designed for you to  collaborate with other customers / end users of the product. It is  monitored by TAC support from time to time but if you need support, a  case should be submitted to the TAC for assitance.
Adapter logging is driven by the 'Host Environment Log' setting on the master connection (go to connections and edit the master connection). If you set this to 'High Debug', you will get high debug logging for the adapters under the ../master/services//log. For JDE, the GUID is {DDEB44A7-4377-41E9-AF20-BFA8177B1B9D}. Therfore the path for the JDE adapter logs can be found on the master server in the ../Master/services/{DDEB44A7-4377-41E9-AF20-BFA8177B1B9D} directory.
John
Tidal Enterprise Scheduler TAC