Skip to main content

Community, 

we have couple migration job scheduled running every night. and then using IFS SFTP job to deliver the file to remote FTP folder. But recently we realized the SFTP job failed every time. please see the screenshot attached.

We tried to have the SFTP job disabled and do manually step by step, it is working well.

our file is generated by migration job, and have it kept on DB FTP folder. due to large amount of data, it will take roughly couple minutes to complete one migration job.

The most possible reason we could imagine is, when migration job is started, the file is appeared in the folder with 0 bytes. in the meantime,  SFTP job is triggered, thus it is sent with an empty body, and leads to the failed message.

wondering anyway we could let the system not send the empty file until the migration job is completed.

Thank you.

HI @ronhu ,

 

Can’t you adjust time between two jobs to finished the migration job before SFTP job.  Is there any difficulty for that ?

@Dumeesha Wanigarathna Thank you for your input.

this is an option, I agree, but this option cannot really fix this issue permanently. Migration job and SFTP jobs there is no reconciliation mechanism between 2 jobs. So there is no guarantee when migration job is running, SFTP job is not going to be triggered. 

another option is to try to give a temp file name for the migration job, when the job is completed, i.e. the file size in the FTP folder is >0, then trigger a window task to rename it to an official file name which could be recognized by SFTP jobs. 

We are working with IFS Cloud team to see the possibility to have the window task done.

Thank you.

Terms & ConditionsCookie settings