After changing up my mono-repo structure the warning has now become an error

Mar 31, 05:52:47 PM: e861114c ERROR Error: ENOENT: no such file or directory, mkdir '/var/task/myapp/.next/cache'
at ignore-listed frames {
errno: -2,
code: 'ENOENT',
syscall: 'mkdir',
path: '/var/task/myapp/.next/cache'
}

Mar 31, 05:52:47 PM: e861114c WARN This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Mar 31, 05:52:47 PM: e861114c ERROR Error: ENOENT: no such file or directory, mkdir '/var/task/myapp/.next/cache'
at async Object.mkdir (node:internal/fs/promises:856:10)
at async /var/task/node_modules/next/dist/server/lib/disk-lru-cache.external.js:36:17
Mar 31, 05:52:47 PM: e861114c ERROR ⨯ unhandledRejection: Error: ENOENT: no such file or directory, mkdir '/var/task/myapp/.next/cache'
at ignore-listed frames {
errno: -2,
code: 'ENOENT',
syscall: 'mkdir',
path: '/var/task/myapp/.next/cache'
}

Does anyone have any info on why this could happen?

I've found the issue.

Bots keep going to _next/image without an image and without params

and it's causing cache issues in netlify, is there any way to prevent bots from doing this?