Description of bug: When adding a scheduled task from the CF Administrator interface, the RequestTimeout parameter is not appended to the URL when CF runs the task - which in our case made the request timeout quicker than specified.

Comments: The workaround for us was to just add '&RequestTimeout=3000' to the actual URL called from the scheduled task instead of putting '3000' in the RequestTimeout form field. This is a bug in CF5 since after upgrading from 4.5 our data feeds no longer worked even though the form field in the administrator said the correct RequestTimeout. Once we hard coded the RequestTimeout param in the URL it worked again.

--->

A D D     Y O U R     C O M M E N T S     T O     T H I S     B U G

Please login to add comments to a bug

C O M M E N T S Comment display is being revamped. We apologize for the delay. Not Reproducible   [Michael Dinowitz]   [ ] I use the scheduler on a per minute basis to run the CF-Talk and other mailing lists. The url that is called has a 110 second request timeout on it. This timeout was set in the proper box on the control panel. I also have some heavy custom error handlers running to catch ANY error. When a timeout is called, I get an error message saying that the timeout occured.