Cloud Scheduler Status: Internal

Hi Community,

Anyone of you guys ever got this error while trying to run a Cloud Scheduler?:

httpRequest{1}
insertId
jsonPayload{
type"type.googleapis.com/google.cloud.scheduler.logging.AttemptFinished"
debugInfo"URL_UNREACHABLE-UNREACHABLE_5xx"
jobName
status"INTERNAL"
targetType"HTTP"
url
 
logName"projects/big-query-264413/logs/cloudscheduler.googleapis.com%2Fexecutions"
receiveTimestamp"2024-04-22T08:00:03.309113451Z"
resource{2}
severity"ERROR"
timestamp"2024-04-22T08:00:03.309113451Z"
 
0 8 715
8 REPLIES 8

Hello @AbbasB,

Welcome to the Google Cloud Community!

Your issue seems to be caused by an unreachable URL that returned a 5xx server error. Please verify the URL in your Cloud Scheduler job is correct, accessible online (if it's public), and that the server it points to is working properly.

Also consider re-enabling the Cloud Scheduler API, redeploying your Cloud Function, and resuming your Cloud Scheduler job.

Hello AbbasB

Same, problem since this week.

We will try the solution proposed by Juliadeanne

 

Hello, everyone!

Did the steps work for you? I have the same problem and can't find the reason why the cloud scheduler job can't trigger the cloud function.

Thank you!

For me problem seemed to be in the function itself. I have 2 cloud scheduler jobs running and I had to fix my functions, test them and try running again. Basically, I had some errors in my functions. Make sure to test you functions in cloud functions.

Hello, everyone!

I have the same issue with my Firebase Function for scheduler

I have the same issue... a scheduled job has been running successfully for ages and I made a minor change not affecting the url and now it fails every time with the unreachable url error. A similar function that I havent edited is still working

I disabled the API , paused and resumed the scheduler, still getting the same error , "debugInfo":"URL_UNREACHABLE-UNREACHABLE_5xx"

As @mokhinurra1 suggests above, check your function for errors. I think the URL_UNREACHABLE error is misleading, when I looked at the execution logs for my function I actually found issues with the code. When I fixed those, the scheduled job ran as expected