Response Data Too Big on Cron-Job.org about cron-job.org

[pschlan]

Please change your URL/script to return less data. cron-job.org accepts up to 4 kB of response data from your URL/script. Usually it's enough to send just a short status code like "OK" after script execution.

[gujingc]

pschlan, we are seeing the problem. Our cron jobs have been running perfectly for 2 years and all in a sudden this starts to show.

We are using wp-cron.php. I do not know how to change the script. Please advise.

[gujingc]

Pschlan, this is what we found.

We did our tests twice.

• We first keep the Cron jobs enabled. Then we click on the Test Run button. All failed
• Then we turned off the button to disable the crob jobs. Then we clicked on the test run. All successfully passed the test. Then we we back enabled the cron jobs.

We are not technical. But this looks interesting.

[pschlan]

Can you send the account email address to [email protected], referencing this issue?

[boxster1]

We are having the same issue, the job ran fine for months now it fails. What do we need to do?

[gujingc]

I switched to the Easy Cron, or you can use Google Scheduler. Very small cost. The issue went away. Google Scheduler might be the best option out there. EasyCron is not bad at all. You pay $1 / month to handle multiple jobs. Google Scheduler could be even cheaper. The issue seems to be the text size allowed.

…

On Wed, Nov 10, 2021 at 7:25 PM boxster1 ***@***.***> wrote: We are having the same issue, the job ran fine for months now it fails. What do we need to do? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#53 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZRZ3KS6GPQGV6UJ3P3FMLULMZTXANCNFSM4JLYE6QQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[pschlan]

I still fail to see why a cron job would need to output that much data/text. If it’s logging information, it should rather go to a log file than to the browser/HTTP output.

Switching to a service which has a higher limit on output data seems like a workaround, not a solution. If your job‘s output amount depends on the work it’s doing, you might sooner or later run into this issue again, even with a higher limit on other services.

[gujingc]

Patrick, Understood. We all have a million things. And if this is something that spending a dollar a month could bring a closure, it is worth giving it a try. At the same time, I for one did not change a thing on my site when this happened.

…

On Wed, Nov 10, 2021 at 10:54 PM Patrick Schlangen ***@***.***> wrote: I still fail to see why a cron job would need to output that much data/text. If it’s logging information, it should rather go to a log file than to the browser/HTTP output. Switching to a service which has a higher limit on output data seems like a workaround, not a solution. If your job‘s output amount depends on the work it’s doing, you might sooner or later run into this issue again, even with a higher limit on other services. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#53 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZRZ3M453POSKKFB5OVAF3ULNSBPANCNFSM4JLYE6QQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[pschlan]

Aligns with my theory that the output size is too dynamic. And also means that it could happen again any time if the root issue is not addressed.

Closing this issue as there’s no indication of a bug on our side.