Dropdown to select Datatables not populating properly

[gwhitson]

Describe the problem/error/question

Worth noting that our n8n instance is running from an Azure Web App in a GCC High tenant.

After opening a workflow from the 'Overview' tab, nodes interacting with a datatable are not populating the list of tables to choose from or columns in the table. If opening the workflow from the personal tab, the fields are populating properly.

What is the error message (if any)?

No error message just lack of data

If there is a table already in the dropdown, it doesn't remove it automatically, however doing a reset value and refresh list puts it back to the state where no table is selectable.

Going to the same area if you selected the workflow from 'Personal' rather than 'Overview', the dropdowns populate correctly

Please share your workflow/screenshots/recording

{
"nodes": [
{
"parameters": {
"workflowInputs": {
"values": [
{
"name": "name"
}
]
}
},
"type": "n8n-nodes-base.executeWorkflowTrigger",
"typeVersion": 1.1,
"position": [
0,
0
],
"id": "adec2a94-7833-48ef-81a1-acfb3e3f9fda",
"name": "When Executed by Another Workflow"
},
{
"parameters": {
"operation": "get",
"dataTableId": {
"__rl": true,
"mode": "list",
"value": ""
}
},
"type": "n8n-nodes-base.dataTable",
"typeVersion": 1.1,
"position": [
208,
0
],
"id": "bc278905-5c36-4f97-acda-6ae1ce8cbebb",
"name": "Get row(s)"
}
],
"connections": {
"When Executed by Another Workflow": {
"main": [
[
{
"node": "Get row(s)",
"type": "main",
"index": 0
}
]
]
},
"Get row(s)": {
"main": [
[]
]
}
},
"pinData": {},
"meta": {
"instanceId": "c388d94a0ab7f356db396f5c1531a4ec99e75f899658d9fa41ff41c0aae96b36"
}
}

Debug info

core

• n8nVersion: 2.9.4
• platform: docker (self-hosted)
• nodeJsVersion: 24.13.1
• nodeEnv: production
• database: postgres
• executionMode: regular
• concurrency: -1
• license: enterprise (production)

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/145.0.0.0 safari/537.36 edg/145.0.0.0
• isTouchDevice: true

Generated at: 2026-02-26T14:06:53.381Z}

[n8n-assistant]

Hey @gwhitson,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-7023".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-7023

[disassembledd]

Thanks for opening the issue @gwhitson. I've tried reproducing your issue and am unable to. What I have done is create a simple data table called Test1, created a new workflow, added a Data Table node to insert and left the dropdown empty, then I attempted to open it from the "Personal" section and the "Overview" section and I cannot get it to behave the way you're experiencing.

I see your deployment scenario is very unique and not easily replicated if it is related to your issue, and that you are an enterprise user. As such, I would suggest reaching out to official n8n support for assistance with this issue. They should be able to raise it internally if they deem it to be an issue within n8n rather than your deployment.

#closed:support-issue

[lucasplcorrea]

Thanks for opening the issue @gwhitson. I've tried reproducing your issue and am unable to. What I have done is create a simple data table called Test1, created a new workflow, added a Data Table node to insert and left the dropdown empty, then I attempted to open it from the "Personal" section and the "Overview" section and I cannot get it to behave the way you're experiencing.

I see your deployment scenario is very unique and not easily replicated if it is related to your issue, and that you are an enterprise user. As such, I would suggest reaching out to official n8n support for assistance with this issue. They should be able to raise it internally if they deem it to be an issue within n8n rather than your deployment.

#closed:support-issue

GOAT, works for me!