This issue comes up if a file reader is inside a loop, leading to typing problems. I haven't thoroughly tested it with different readers, but I known for sure that the CSV Reader has this behaviour.
A workaround lies in using a Table Validator, but defaulting to strings is just... nonsense.