Edge Function Logs Not Appearing in Supabase Dashboard (Function Executes Successfully) #36683
Replies: 13 comments 1 reply
|
I've been experienceing the exact same issue for the past 48 hours approx. No logs for non of my edge functions when they were working perfectly before |
|
I'm having the same issue here. It was working fine, but now it's no longer working. Even when I manually try to run something as simple as the query below, I get an error in the log explorer (does not load the logs through the UI as well). select Error fetching logs: |
|
Also experiencing the exact same issue. No code changes in months, suddenly no logs or observability to my edge functions despite them running. |
|
I'm experiencing the same problem! It was working normally until yesterday, and suddenly it stopped recording. I tested it with a new edge function, and the same behavior persisted. If any kind soul has a solution, please help us out! |
|
I have the opposite problem. The updates I make from within the Supabase dashboard actually work, whereas the updates I make in code and deploy with the CLI aren't included |
|
I have the same problem. It's not showing logs if invoked from outside of supabase website |
|
same problem here!!! |
|
I seem to have the same issue. I patched the edge function in question with a Deno.serve(async (req) => {
console.log('Test');
...
});in the first line. I can see the code updated correctly in the "Code" tab of the function. |
|
Yes i see that the data is not loading in the frontend via edge function.
When we go to the code the edge function say that failed to load function
code
[image: image.png]
…On Thu, Dec 18, 2025 at 4:36 PM Moritz Becker ***@***.***> wrote:
I seem to have the same issue.
I patched the edge function in question with a
Deno.serve(async (req) => {
console.log('Test');
...});
in the first line.
I can see the code updated correctly in the "Code" tab of the function.
I can see invocations to the function in the "Invocations" tab.
Yet, I see 0 log entries in the "Logs" tab.
—
Reply to this email directly, view it on GitHub
<#36683 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BNYN6FZ6ZUY3Z6W7WBBFAVL4CKDENAVCNFSM6AAAAACAFBOYICVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMRYHA2DSNY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Dear Team,
It has been 3 hours the code is not visible and the frontend is not able to
load. Can you please urgently check the problem ?
My Organisaiton name is Shivtel Communications pvt ltd
[image: image.png]
|
|
please see one more screen shot
[image: image.png]
…On Thu, Dec 18, 2025 at 7:38 PM Nitish Gopalani ***@***.***> wrote:
Dear Team,
It has been 3 hours the code is not visible and the frontend is not able
to load. Can you please urgently check the problem ?
My Organisaiton name is Shivtel Communications pvt ltd
[image: image.png]
|
|
***@***.***
…On Thu, Dec 18, 2025 at 7:38 PM Nitish Gopalani ***@***.***> wrote:
Dear Team,
It has been 3 hours the code is not visible and the frontend is not able
to load. Can you please urgently check the problem ?
My Organisaiton name is Shivtel Communications pvt ltd
[image: image.png]
|
|
False alarm in my case, everything works correctly. |
Uh oh!
There was an error while loading. Please reload this page.
I'm experiencing an issue where the logs of my Edge Function are no longer visible in the Supabase dashboard but the functions are working properly.
Issue:
The function is deployed successfully and executes as expected (returns proper responses).
However, no logs are shown in the Logs tab under Edge Functions, even though:
I've added multiple console.log() and console.error() statements in the function.
Log filters (time range, severity) are correctly set.
I tried querying function_logs manually via the SQL Editor, but it returns nothing.
Also tried creating a new dummy function with logs — same result: no logs visible.
I’ve already tried redeploying the function and using the CLI (supabase functions deploy), but the problem persists.
Question:
Is this a known issue or is there a workaround? Could the logging pipeline (Logflare) be broken on this project?
Would appreciate any help or direction on resolving this.
Thanks!
— Nitish
All reactions