Could it be a timeout issue? Perhaps try increasing the two timeouts in the HTTPCaller, look under the section HTTP Client Options.
Could it be a timeout issue? Perhaps try increasing the two timeouts in the HTTPCaller, look under the section HTTP Client Options.
You miiight also get a little more information from the log if you turn on DEBUG logging in the options. Note: This is only recommended for web based debugging. Ignore everything else including BADNEWS. BADNEWS is fine.
Once you have figured out the issue then turn debug logging back off
You miiight also get a little more information from the log if you turn on DEBUG logging in the options. Note: This is only recommended for web based debugging. Ignore everything else including BADNEWS. BADNEWS is fine.
Once you have figured out the issue then turn debug logging back off
Agree completely about using debug mode here.
On a side note, I'd love to have a chat with the poor soul that decided that printing "BADNEWS" for non-critical debug messages was a good idea I can't count the number of clients I've had to assure that no, it's not really bad news for your translation!