Edge function frequently returns 504
I'm calling an edge function from a stored function via the net.http_post extension. These calls are async so the execute and move right on.
In my main Edge Function logs, for every 10 successful invocations, I see about 4 that are 504. Looking at the actual edge function logs, I'm not seeing any errors and as far as I can tell, the functions are booting and shutting down properly. Furthermore, all the things I expect to see happening in the edge function, are happening.
The reason this is a problem is because the jobs being processed are seeing the 504 and acting as if the job failed, so they aren't moved to the archive but their "seen" count increments. Thus, I'm wasting lots of cycles re-processing jobs that ultimately return "already been processed".
What in the world could be causing these 504 responses? At this point I'd be happy to pay for support if someone can actually figure this out. Thanks.
Ted Stresen-Reuter
In my main Edge Function logs, for every 10 successful invocations, I see about 4 that are 504. Looking at the actual edge function logs, I'm not seeing any errors and as far as I can tell, the functions are booting and shutting down properly. Furthermore, all the things I expect to see happening in the edge function, are happening.
The reason this is a problem is because the jobs being processed are seeing the 504 and acting as if the job failed, so they aren't moved to the archive but their "seen" count increments. Thus, I'm wasting lots of cycles re-processing jobs that ultimately return "already been processed".
What in the world could be causing these 504 responses? At this point I'd be happy to pay for support if someone can actually figure this out. Thanks.
Ted Stresen-Reuter
