Torgil Zethson wrote:When you do a Test Transformation, the client sends a request to the Jitterbit server, and then waits for the server to send back the result of the test. If this takes too long, the call will time out, which is what you are experiencing.
Currently, the timeout is hardcoded, so there is unfortunately no way to increase it (other than rebuilding the client). We will look into the effort it would take to make this property configurable - let me get back to you on that.
The next question is why the test takes so long. The current value of the timeout is 10 minutes (I think), which is usually sufficient. Are you transforming very large amounts of data?
The text file itself is only 194KB, but each row can have up to 256 mappings to a field within the source file. I don't know if that will slow down things.