Executed the SS again, and checked the data, and compare it to the data in BY, as per checking, the specific transfer number status is set to W meaning created in the BY, but not in the MySQL, updated the tag and status field in MySQL and set it into Y and W, then executed the screen scrape again, as per checking, the execution continues and updated many transfers status into W (created status), checked the previous transfer updated to see what is the cause of it to not continue previous execution, while the execution just now is still running.
Checked if the execution is finished it is finished but the last transfer created status in MySQL is not updated into W and the tag has no Y value as per checking, checked the data and the cause of this, but the data meet all the conditions in the screen scrape thus the execution should not be stopped. 
Executed the SS again to see if it will not continue to the next transfer same to the previous problem encountered, but as per checking of the execution, it is continuing and executing the next transfers though the transfer where is stopped still not updated but the next transfers are updated. Compared the transfer where it stopped and the next transfer to see if the data needs in the screen scrape have a difference and it has no difference with the next transfer, suspecting that the possible cause is the connection is losing thus the process is stopped and the data is not updated in MySQL.
Encountered the same problem again, the execution stopped, the transfer it was creating is not updated into the created status, executed the SS again, the execution continues to the next transfer and the status and tag are updated and the transfer it stopped still not updated, the possible problem is the connection of SS into blue yonder is losing, the screen scrape sometimes attempting to connect in BY but can't connect thus stopped the execution. This will be checked further for confirmation of the findings.