No way of catching: [ERROR] ActionNotFoundError: The server received a request for an action named `..........` but could not find a match.

[xriter]

Astro Info

Astro                    v5.6.0
Node                     v18.20.3
System                   Linux (x64)
Package Manager          npm
Output                   server
Adapter                  @astrojs/node
Integrations             none

Describe the Bug

We've been seeing the following error a lot in our server logs recently:

15:01:59 [ERROR] ActionNotFoundError: The server received a request for an action named `..........` but could not find a match. If you renamed an action, check that you've updated your `actions/index` file and your calling code to match.
    at AppPipeline.getAction (file:///app/dist/server/chunks/_@astrojs-ssr-adapter_T2VsY-t8.mjs:276:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.handler (file:///app/dist/server/chunks/index_DhTrmX1a.mjs:995:28)
    at async Module.POST (file:///app/dist/server/pages/_actions/_---path_.astro.mjs:9:18)
    at async renderEndpoint (file:///app/dist/server/chunks/astro/server_Bdd2vCsi.mjs:487:18)
    at async lastNext (file:///app/dist/server/chunks/index_DhTrmX1a.mjs:1979:23)

(The action name '........' is actually this value, so I did not obscure it or something. (In case this matters)).
I think these are bots that are trying to break the system somehow.

There currently doesn't seem to be a way to catch these errors more gracefully (update: not even in middleware it seems!), like sending these requests to a 404 page or to run any other code in case an action is not found.

Maybe in the actions setup, there should be a 'onNotFound' property or something, that gets called if an action is not found?

import { ActionError, defineAction } from 'astro:actions';

export const server = {
  hi: defineAction({
    handler: async () => {
      return 'Hi';
    },
  }),
onNotFound: (data, ctx) => {
 // do something like maybe blocking the ip, or adding it to a ban-list...
return Response({}, { status: 404 });
}
};

What's the expected result?

So not so much a different expected result, but more the wish to catch these errors somehow to be able to act upon them.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-1shwwyyj?file=src%2Fpages%2Findex.astro

Participation

• I am willing to submit a pull request for this issue.

[xriter]

Anyone else experiencing this? Still receiving many error logs from this error, and there's no way of debugging it right now...

[matthewp]

You can use a middleware but this does seem a little unexpected to me, I would expect either a 404 or something else in the 400 range.

[xriter]

Up till today I still daily see this error message. It is always the value "..........", never any other action that is not found. The code never literally calls ".........." as an action endpoint. But it always being this same value, makes me wonder whether this is actually a bot at work or something else.

I am not sure how to approach this. Could there be a deeper issue/bug?

[xriter]

You can use a middleware but this does seem a little unexpected to me, I would expect either a 404 or something else in the 400 range.

@matthewp
I remember now: I did try debugging this by trying to catch it in a middleware. But for some reason it is not catched by the middleware.

I have:

// src/middleware.ts
export function onRequest(context, next) {
  try {
    return next();
  } catch (e) {
    // We don't reach this point
    console.log('an error occured');
    console.log(e);
    console.log('further request debugging here');
  }
}

and all I can see in the console is:

02:20:33 [WARN] [router] No API Route handler exists for the method "POST" for the route "/_actions/.......".
Found handlers: "default", "file", "url"

02:20:33 [ERROR] [router] Error: The server received a request for an action named `.......` but could not find a match. If you renamed an action, check that you've updated your `actions/index` file and your calling code to match.
    at getAction (/Users/.../node_modules/astro/dist/core/base-pipeline.js:81:15)
    at processTicksAndRejections (native)
02:20:33 [500] POST /_actions/....... 691ms

So if I can't catch the Error in the middleware, then how to debug this further?