Chron job calls edge function: 401 status code; authorization header not working?

[dev-firstlvlpets]

Hey all,

I am using the free plan of supabase and following this guide: https://youtu.be/miRQPbIJOuQ?t=349 I setup my hello-world edge function, enabled chron integration and pg_net, and created a chron job to call my edge function without specifying the anon key since the guide tells me it is not required.

However, in the edge function logs I receive 401 status code when calling it now.

When I disable requiring the JWT verification it my chron job can call the edge function successfully.

But when I require the JWT verification again and if I specify the anon key manually as a HTTP header it still does not work.

To me something looks off here. Does someone has an idea what is going on here?

And here is the 401 log message, no auth header provided *at least here in the log.:

{
  "event_message": "POST | 401 | https://ABC.supabase.co/functions/v1/hello-world",
  "id": "35acc423-53a4-43b5-89d9-bcb60bf0b04c",
  "metadata": [
    {
      "deployment_id": null,
      "execution_id": null,
      "execution_time_ms": 260,
      "function_id": null,
      "project_ref": "ABC",
      "request": [
        {
          "headers": [
            {
              "accept": "*/*",
              "accept_encoding": "gzip, br",
              "connection": "Keep-Alive",
              "content_length": "15",
              "cookie": null,
              "host": "ABC.supabase.co",
              "user_agent": "pg_net/0.8.0",
              "x_client_info": null
            }
          ],
          "host": "ABC.supabase.co",
          "method": "POST",
          "pathname": "/functions/v1/hello-world",
          "port": null,
          "protocol": "https:",
          "sb": [],
          "search": null,
          "url": "https://ABC.supabase.co/functions/v1/hello-world"
        }
      ],
      "response": [
        {
          "headers": [
            {
              "content_length": "83",
              "content_type": "application/json",
              "date": "Thu, 30 Jan 2025 12:55:01 GMT",
              "server": "cloudflare",
              "vary": "Accept-Encoding",
              "x_sb_compute_multiplier": null,
              "x_sb_edge_region": "eu-central-1",
              "x_sb_resource_multiplier": null,
              "x_served_by": "supabase-edge-runtime"
            }
          ],
          "status_code": 401
        }
      ],
      "version": null
    }
  ],
  "timestamp": 1738241701127000
}

[GaryAustin1]

You have bearer: jwt. It is bearer jwt.

[dev-firstlvlpets]

Thanks, that did the trick. I overlooked it.

Should that be included automatically or mentioned in the Supabase UI when setting up a chron job calling an edge function? Since the guy from the Youtube video did not mention it.

[GaryAustin1]

It is not included when you use pg_net. He must have the jwt required off in his edge function like you turned off.