<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=440810&amp;fmt=gif">

Fixing that Scheduler would stop running a Transfer (version 3.2.89b)

By Michael Bock - July 02, 2014

In Rapidi we have an internal flag on a Transfer that tells if a Transfer is currently running. This is used to ensure that the same transfer is not started twice - for example that the Scheduler started the Transfer and then the transfer is stated manually also.

In some error situations - notably after getting a TRA_UnknownError this flag was not reset correctly. Next time the Scheduler was trying to run that transfer, you would get a TRA_TransferAlreadyExecuting error.

We now ensure that this TransferRunning flag is correctly reset in any error situation and the Scheduler is always able to try to run the transfer again.

version 3.2.89b (02-07-2014)


About the author

Michael Bock

Picture of
Michael founded Rapidi on technological excellence, fantastic customer service and continuous improvement. A data integration specialist since 1987, he remains focused on creating technology that solves real business problems.


SHARE