N8N 節點 - 稽核問題

描述問題/錯誤/問題

當使用 N8N 節點,其中資源設定為 Audit,操作設定為 Generate,類別設定為 Instance 時,我持續收到錯誤訊息。這只是在升級到版本 2.32.6 之後才開始發生的。在此更新之前它是正常運作的。

錯誤訊息是什麼(如果有的話)?

{
“errorMessage”: “服務無法處理您的請求”,
“errorDescription”: “內部伺服器錯誤”,
“errorDetails”: {
“rawErrorMessage”: [
“請求失敗,狀態碼為 500”
],
“httpCode”: “500”,
“errorData”: {
“message”: “內部伺服器錯誤”
}
},
“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: 服務無法處理您的請求”,
" 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"
]
}
}

關於您的 n8n 設定的資訊

  • n8n 版本:2.32.6
  • 資料庫(預設值:SQLite):SQLite
  • n8n EXECUTIONS_PROCESS 設定(預設值:own, main):預設
  • 執行 n8n 的方式(Docker、npm、n8n cloud、桌面應用程式):Docker
  • 作業系統:Ubuntu Linux

@MattyJ2009,當你等待回應時,這些東西可能會有所幫助:

建議的資源

自動匹配你的問題。

文件:

論壇:

@pranicvivek - 你以前幫助過類似的問題,能看一下嗎?

由 n8n 社群機器人自動建議。這是試點 - 請在此分享反饋

聽起來像是退化問題。
也許你想提交錯誤報告?

感謝您讓我們知道這一點。我們已建立 CV-56 作為內部開發工單來進行調查。

感謝你讓我們知道這一點,我們已建立 CAT-3896 作為內部開發票證來調查此問題。

感謝您回報此迴歸問題。

今天已在 fix(core): Import security audit risk reporters with a file extension by looorent · Pull Request #35263 · n8n-io/n8n · GitHub 中修復。這將被向後移植到下一個 2.32.x 版本中。