Intermittent error message in ION "Unable to create file for message:5fd5832af5164b7ea6e5c240c1e7d0a

I have a data flow configured in ION that runs daily to pick files generated in WFM and send it out to a destination sFTP (globalscape).

Since its activation, we have been observing intermittent issues with successful end to end processing of these files. The destination sFTP receives files twice at their end intermittently for this data flow. We observed that ION runs into authorization issue in these cases while creating files in destination sFTP at first place. Event Type and error Reason message captured below for reference. On retry in a few seconds, it eventually successfully places another file which is successfully processed in destination sFTP.

Event Type: Delivery failed, retry started
Error Reason: Unable to create file for message: 5fd5832af5164b7ea6e5c240c1e7d0a2

While the second file is successfully processed, the first file that reaches destination sFTP fails and continues to stay in their root folder.

Destination sFTP has a common username configured with FULL authorization access that's maintained in the connection point of this data flow.

Seeking help if anyone ran into a similar issue in past or able to suggest anything we can try for resolution?

Thanks in advance!

Dev

Find more posts tagged with

ION Connect

Accepted answers

All comments

Brandon Balkenhol

We have single tenant WFM with multi-tenant HR Talent - two seperate SFTP servers. When I originally set up ION to pick up our payroll export file from the WFM SFTP server and transfer it over to the HR Talent server for processing, I ran into some odd errors like you are describing. I finally came to the conclusion that ION was picking up the file from WFM before the WFM job was complete. For files we send out of WFM now, I have an SFTP task on that WFM job to push the file directly over to the HR Talent SFTP when the other tasks are complete. This ensures writting to the file is complete before the file is moved.

It sounds like you're pushing yours outside of the Infor ecosystem for processing. In your case, you could create a different directory on your own WFM SFTP server for files intended to be picked up by ION. Then set up on your WFM jobs an extra step at the end to push the file to that separate directory on the same SFTP server.

Dev Ballani

@Brandon Balkenhol - Thank you for sharing your experience. I have MT WFM, with no access to WFM sFTP servers. Do you think I can achieve something similar in our instance?

Brandon Balkenhol

There may be a better way to accomplish this same thing that would be more ideal - such as scripting. If Infor had a method of just moving or renaming the file when processing was finished, this wouldn't be an issue. Maybe someone here has a better solution for accomplishing this.

If you don't have access to the MT SFTP server, then you may want to talk to someone in your organization that does have this access. The set up for the File Transfer Endpoints needed for the Secure File Transfer Task is located at "Maintenance" > "System Administration" > "File Transfer Endpoints". When you create a new endpoint, you could use the same information on the ION Connection Point that is currently picking up this file.

One thing to be aware of is that if there is a data refresh from Prod to your Testing tenant, then the Prod connection will remain and will need to be updated. The other thing to be aware of is that if the password used for the ION connection changes, then this will need to be updated as well. Some organizations require these passwords to be rotated for security compliance. If you don't have access to the MT SFTP server now, then you may not be the one that sets this up or maintains it in the future.

Kevin Heiman

Some considerations, if i read this correctly.…

is there a log on the target FTP site that can tell you what is occurring, why the write is failing? It would seem that some timing or authentication process is not completing and the error occurs, and then ION will retry and it works.
if you manually do the steps, are you getting similar errors when writing the file to the SFTP site?
Are you using the Overwrite option?
Would using the scenario to write to a read only directory be a consideration? This option removed the additional steps the connector does to write a file. You would need to monitor for failures.

for the read side some thoughts. although read is not seemingly related to this.

If the read of the source file is the problem, could you have the process create the file, then when done rename the file so that it gets picked up? if a partial file is the problem, which I don't think it is in this case. You would see that in Oneview as well.
consider a less frequent polling interval,
have the producer of the file, also send a 'signal' BOD that would invoke the Dataflow to process the FTP.

I think the logs of the target site are your best option.

Copyright © 2025 Infor. All rights reserved.