The 65000 USD question from this migration and the manually stepped FAHB uploading... first the trickle files, then after longer wait allowing the trickles messages to go up and seeing 100% success rate , at least on the one big cruncher account, why in regular production we get these incessant invalid if even for a little while the crunching takes place off-line. It does appear to me that trickle messages MUST come AFTER trickle files go up, in any order the client seems fit in doing. Thusly, just maybe something in the way of telling the client to back off reporting trickle messages long as trickle files are still in queue and or, do not process trickle messages on the server side, in proper order, until the matching trickle files have good and well arrived, but the order in-which is the issue to crack.

Would the techs kindly revisit the issue and conclusively give us a long avoided answer and solution. (I was one of yeah of little faith in the matter, and still am).

Thanks