500 Internal Server Error when listing rows via API (n8n) with AND + OR filter groups on Big Data tables

Developer Talk API
1

Description

When using the SeaTable API via the n8n SeaTable node (“Get many rows / List rows”), we consistently get a 500 Internal Server Error if the view contains AND filters combined with an OR filter group.

Observed behavior

  • Listing rows without any filters works
  • Listing rows with simple filters only (no filter groups) works
  • Listing rows with AND filters that include an OR group (e.g. A AND (B OR C OR D)) fails with HTTP 500
  • The same table works immediately if the filters are removed or simplified

Environment

  • Integration: n8n (SeaTable node, “Get many rows”)
  • SeaTable self-host
  • API: List Rows

Error message returned by the API

{
  "errorMessage": "The service was not able to process your request",
  "errorDescription": "internal server error",
  "errorDetails": {
    "rawErrorMessage": [
      "500 - {\"error_message\":\"internal server error\"}"
    ],
    "httpCode": "500"
  },
  "n8nDetails": {
    "nodeName": "Get many rows",
    "nodeType": "n8n-nodes-base.seaTable",
    "nodeVersion": 2,
    "resource": "row",
    "operation": "list",
    "itemIndex": 0,
    "time": "14.12.2025, 21:07:15",
    "n8nVersion": "1.123.5 (Self Hosted)",
    "binaryDataMode": "filesystem",
    "stackTrace": [
      "NodeApiError: The service was not able to process your request",
      "    at ExecuteContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1498:10)",
      "    at processTicksAndRejections (node:internal/process/task_queues:105:5)",
      "    at ExecuteContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1798:11)",
      "    at ExecuteContext.seaTableApiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/SeaTable/v2/GenericFunctions.ts:129:10)",
      "    at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/SeaTable/v2/actions/row/list.operation.ts:87:22)",
      "    at ExecuteContext.router (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/SeaTable/v2/actions/router.ts:25:20)",
      "    at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@aws-sdk+credential-providers@3.808.0_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/SeaTable/v2/SeaTableV2.node.ts:25:10)",
      "    at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1045:8)",
      "    at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1226:11)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@opentelemetry+api@1.9.0_@opentelemetry+sdk-trace-base@1.30_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1662:27"
    ]
  }
}
2

This is a known issue and will be fixed soon.

1 Like
3

On our side (Seatable cloud), all the forms and our universal apps (which contains forms, but not only) are down. The forms give this error message:

Page unavailable

Sorry, but the requested page is unavailable due to a server hiccup.

Our engineers have been notified, so check back later.

The universal app gives this one:

Erreur interne du système

(which means System’s internal error).

Good to know the issue will be fixed soon, we are crossing our fingers.

4

Hello, on our side the issue remains, do we have an estimated time/day of when it will be solved so that we can let people using our service now?

Thank a lot,

Best

5

intermittent issue with this. We have certain automations in make dot com that are throwing errors

6

Are you reporting a general issue?

The original post is about a specific API issue.

7

Hi ralph,

The keyword here is “500 internal server”. All day I have had timeout issues on my makedotcom scenarios, all caused by SeaTable. I thought this was a report about that. It is affetcing two Cloud Enterprise accounts I manage.

8

There are two issues here:

9

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.