N8N Node - Audit Issue

Questions
1

Describe the problem/error/question

When using the N8N node where resource is set to Audit and operation is set to Generate and categories is set to Instance, I keep getting an error message. This only started happening when I upgraded to version 2.32.6. It worked prior to this update.

What is the error message (if any)?

{
“errorMessage”: “The service was not able to process your request”,
“errorDescription”: “Internal server error”,
“errorDetails”: {
“rawErrorMessage”: [
“Request failed with status code 500”
],
“httpCode”: “500”,
“errorData”: {
“message”: “Internal server error”
}
},
“n8nDetails”: {
“nodeName”: “n8n”,
“nodeType”: “n8n-nodes-base.n8n”,
“nodeVersion”: 1,
“resource”: “audit”,
“operation”: “generate”,
“itemIndex”: 0,
“runIndex”: 0,
“time”: “7/30/2026, 7:00:15 AM”,
“n8nVersion”: “2.32.6 (Self Hosted)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeApiError: The service was not able to process your request”,
" at ExecuteSingleContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_56f5a5be5f9a76dfbcdc404d6ec4dea5/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helpers/authentication.ts:145:9)“,
" at processTicksAndRejections (node:internal/process/task_queues:104:5)”,
" at ExecuteSingleContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_56f5a5be5f9a76dfbcdc404d6ec4dea5/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helpers/factory.ts:119:11)“,
" at RoutingNode.rawRoutingRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_56f5a5be5f9a76dfbcdc404d6ec4dea5/node_modules/n8n-core/src/execution-engine/routing-node.ts:547:20)”,
" at RoutingNode.makeRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_56f5a5be5f9a76dfbcdc404d6ec4dea5/node_modules/n8n-core/src/execution-engine/routing-node.ts:741:19)“,
" at async Promise.allSettled (index 0)”,
" at RoutingNode.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_56f5a5be5f9a76dfbcdc404d6ec4dea5/node_modules/n8n-core/src/execution-engine/routing-node.ts:250:29)“,
" at ExecuteContext.versionedNodeType.execute (/usr/local/lib/node_modules/n8n/src/node-types.ts:90:18)”,
" at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_56f5a5be5f9a76dfbcdc404d6ec4dea5/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1082:8)“,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_56f5a5be5f9a76dfbcdc404d6ec4dea5/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1382:11)”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_56f5a5be5f9a76dfbcdc404d6ec4dea5/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1855:27",
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+exporter-trace-otlp_56f5a5be5f9a76dfbcdc404d6ec4dea5/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2549:11"
]
}
}

Information on your n8n setup

  • n8n version: 2.32.6
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu Linux
2

Hey @MattyJ2009, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@pranicvivek - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

3

Sounds like a regression.
Perhaps you would like to file a bug report?

4

Thanks for letting us know about this, We have created CV-56 as the internal dev ticket to look into it.

5

Thanks for letting us know about this, We have created CAT-3896 as the internal dev ticket to look into it.

6

Thanks for reporting this regression.

It has been fixed today in fix(core): Import security audit risk reporters with a file extension by looorent · Pull Request #35263 · n8n-io/n8n · GitHub . This will be backported in the next `2.32.x` version.