Airtable node resource locator fails with "No bridge acquired for this context" — Cloud 1.123.69

Questions
1

Hi n8n team,

I’m hitting what looks like a platform-level failure on the Airtable node’s resource locator in a clean workflow. Details below.

Environment

  • n8n Cloud, version 1.123.69
  • Instance: [your instance name]
  • Node: Airtable (n8n-nodes-base.airtable)
  • Credential type: Airtable Personal Access Token API
  • Browser: [browser + version]
  • Date observed: August 9, 2026, ~10:45 AM (UTC-5)

Problem

In a new workflow, an Airtable node cannot load any dynamic data from the Airtable API through the editor UI.

  1. With Base and Table set to “By ID” and Mapping Column Mode set to “Map Each Column Manually”, the node shows: No columns found in Airtable. Retry. Clicking Retry does not change the result.

  2. Switching Base to “From list” produces: Could not load list — No bridge acquired for this context. Call acquire() first.

What I have already ruled out

  • The original credential was returning HTTP 401 (AUTHENTICATION_REQUIRED) from Airtable. I created a brand-new credential of type “Airtable Personal Access Token API” with a freshly issued PAT.
  • The PAT has the scopes required for this operation, including schema.bases:read, data.records:read, and data.records:write, and is explicitly granted access to the target base.
  • I did a hard reload of the editor tab and reopened the node. The bridge error persists.
  • I tested the same credential from an HTTP Request node (v4.3) against https://api.airtable.com/v0/meta/bases using Predefined Credential Type → Airtable API, to isolate credential validity from the resource locator path.

Why I think this is not a credential issue

No bridge acquired for this context. Call acquire() first. is not an Airtable API error message — Airtable returns structured JSON errors (401 AUTHENTICATION_REQUIRED, 403 NOT_AUTHORIZED, etc.). This string appears to originate from an internal n8n layer, and the request seems to fail before it ever reaches Airtable.

The same error string is being reported by other Cloud users over the past several weeks, though on a different surface (MCP Server Trigger tool calls rather than the resource locator). That may point to a shared internal component:

Questions

  1. Is this a known issue on Cloud 1.123.x, and is a fix or rollback available?
  2. Is there a supported workaround that avoids the resource locator entirely while this is open?
  3. Can you confirm whether the “bridge” failure affects only editor-time dynamic loading (dropdowns, column mapping) or also production workflow executions? This matters for whether I can ship the workflow with hardcoded IDs.
2

Hi @brayandrq Welcome!
“No bridge acquired for this context. Call acquire() first.” comes from the V8 isolate in n8n’s vm expression engine, not from Airtable, so the fresh PAT changed nothing and the call never reaches the API. It is fixed in a later release, so move the workspace off 1.123.69. In the Cloud dashboard go to Manage > Workspace > Updates & maintenance, set Release track to Stable, pick the current version in the n8n version dropdown and select Change version. That triggers a one to two minute restart.
On your third question, this only affects editor-time dynamic loading. Nodes already saved with IDs and mapped fields keep executing normally in production, so a workflow shipped with hardcoded IDs is safe.
See this:

3

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

4

I am relatively new to N8N and I’m concerned that what I have built so far may break due to a version change, as I can see two stable versions available: 2.33.7 and 1.123.16. Which of the two versions would you recommend using to minimize disruption and avoid major breaking changes?

5

Read the changelogs

Only you yourself knows what is inside your workflow.

Anyway,

seems like a downgrade. Are you sure you want to do that?

6

You’re right, thank you so much, I upgraded to the lastest stable version and now it’s retrieving all the databases and tables from airtable.

8

New version n8n@1.123.73 got released which includes the GitHub PR 36494.