We've found that several times a day, TeleFlow bombs while trying to remove a file. The only resolution is to manually go in and restart the TeleFlow Server. The help documentation indicates that there should be a failure path (we used the default, out of the box outbound application), but it doesn't appear to be there. Here is the log output:


2008/06/13 11:05:34.578: Elapsed Time: 0.032
2008/06/13 11:05:34.578: [6] SQL End
2008/06/13 11:05:34.578: Handle is '1'
2008/06/13 11:05:34.578: [2] FINISH
2008/06/13 11:05:34.578: Outbound_Main<==UpdateCallStatus
2008/06/13 11:05:34.578: [130] DB Disconnect
2008/06/13 11:05:34.578: [133] Delete File
2008/06/13 11:05:34.578: File name '@PlayWav' evaluates to 'C:\InnovationRXWavs\2847.wav'
2008/06/13 11:05:34.578: Deleting 'C:\InnovationRXWavs\2847.wav'
2008/06/13 11:05:34.578: FAILURE
2008/06/13 11:05:34.578: ERROR: Missing next step
2008/06/13 11:05:34.578: FATAL
2008/06/13 11:05:34.578: Attempting to jump to Fatal Error Global Event label: 'APPLICATION_ERROR'
2008/06/13 11:05:34.578: Setting system variable '@FATAL' to ''
2008/06/13 11:05:34.578: [19] Label
2008/06/13 11:05:34.578: Label: APPLICATION_ERROR
2008/06/13 11:05:34.578: [110] Run Flowchart
2008/06/13 11:05:34.578: Flowchart is 'Exit'
2008/06/13 11:05:34.578: Outbound_Main==>Exit
2008/06/13 11:05:34.578: [1] START
2008/06/13 11:05:34.578: [8] Global Event
2008/06/13 11:05:34.578: Label is 'EXIT_END'
2008/06/13 11:05:34.578: Setting system variable '@FATAL' to 'EXIT_END'
2008/06/13 11:05:34.578: [11] Global Event
2008/06/13 11:05:34.578: Label is 'EXIT_END'
2008/06/13 11:05:34.578: Setting system variable '@HANGUP' to 'EXIT_END'
2008/06/13 11:05:34.578: [13] Compare
2008/06/13 11:05:34.578: First Value '@HOOK_STATUS' evaluates to 'OFF-HOOK'
2008/06/13 11:05:34.578: Second Value is 'OFF-HOOK'
2008/06/13 11:05:34.578: @HOOK_STATUS = OFF-HOOK?
2008/06/13 11:05:34.578: (string):OFF-HOOK = (string):OFF-HOOK?
2008/06/13 11:05:34.578: TRUE
2008/06/13 11:05:34.578: [3] Play
2008/06/13 11:05:34.578: Script code is 'PROB_TECHNICAL'
2008/06/13 11:05:34.578: Script code 'PROB_TECHNICAL' corresponds to file 'Vox\Eng\Scripts\PROB_TECHNICAL.Wav'
2008/06/13 11:05:34.578: Playing 'C:\Program Files\TeleFlow\Applications\Inovations TF\Vox\Eng\Scripts\PROB_TECHNICAL.Wav'
2008/06/13 11:05:40.718: Event: VCEEVN_PLAY_DONE, Finished , msec=6120
2008/06/13 11:05:40.718: Play completed.
2008/06/13 11:05:40.718: [5] Wait
2008/06/13 11:05:40.718: Delay is '500'
2008/06/13 11:05:40.718: Waiting 500 milliseconds
2008/06/13 11:05:41.218: numWaitObjects = 5, WAIT_OBJECT_0 + 2 = 2, ret = 2 - @@@
2008/06/13 11:05:41.218: [6] Play
2008/06/13 11:05:41.218: Script code is 'DISCONNECT01'
2008/06/13 11:05:41.218: Script code 'DISCONNECT01' corresponds to file 'Vox\Eng\Scripts\DISCONNECT01.Wav'
2008/06/13 11:05:41.218: Playing 'C:\Program Files\TeleFlow\Applications\Inovations TF\Vox\Eng\Scripts\DISCONNECT01.Wav'
2008/06/13 11:05:43.765: Event: VCEEVN_PLAY_DONE, Finished , msec=2520
2008/06/13 11:05:43.765: Play completed.
2008/06/13 11:05:43.765: [9] Wait
2008/06/13 11:05:43.765: Delay is '1500'
2008/06/13 11:05:43.765: Waiting 1500 milliseconds
2008/06/13 11:05:45.265: numWaitObjects = 5, WAIT_OBJECT_0 + 2 = 2, ret = 2 - @@@
2008/06/13 11:05:45.265: [10] Hang Up
2008/06/13 11:05:45.265: Hanging up
2008/06/13 11:05:45.296: Event: NCCEVN_CALL_DISCONNECTED
2008/06/13 11:05:45.296: Other party hung up
2008/06/13 11:05:45.296: Event: NCCEVN_CALL_RELEASED
2008/06/13 11:05:45.296: u-Event: NCCEVN_CALL_RELEASED
2008/06/13 11:05:45.296: Event: NCCEVN_STOP_PROTOCOL_DONE, CTA_REASON_FINISHED
2008/06/13 11:05:45.296: Event: CTAEVN_DESTROY_CONTEXT_DONE, Finished
2008/06/13 11:05:45.296: [2] FINISH
2008/06/13 11:05:45.296: Outbound_Main<==Exit
2008/06/13 11:05:45.296: [22] FINISH
2008/06/13 11:05:45.296: End of application.
2008/06/13 11:05:45.296: Already on-hook
2008/06/13 11:05:48.296:


2008/06/13 11:05:48.296: All memory released. Exiting...

Please advise at your earliest, as this affects our outbound SLAs.

Thanks in advance,
Susan

Right-click the Delete File step, and select the "Unhide Action Steps" option. This will reveal the FAIL action step, which you can use to programmatically set the actions to take when the failure occurs.

This seemed to help. Thanks a lot!