Gitpulse
Merged
Size
L
Change Breakdown
Bug Fix75%
Feature15%
Security10%
#27939fix(core): Fixing issues across instance ai (no-changelog)

Instance AI execution queries, workflow previews, and proxy mode fixed

MU
mutdmour
·Apr 2, 2026

Three critical bugs in Instance AI were squashed: execution queries returning empty results, workflow previews failing, and artifact cards showing wrong names—plus proxy-managed settings are now properly gated.

When the AI service proxy is active (configured via license and environment variables), the system now correctly hides Model, Search, and Sandbox settings sections from the UI and rejects attempts to update those fields with a 422 error. This ensures the proxy remains the sole authority over those settings.

The execution adapter was passing accessibleWorkflowIds directly to the query builder, but that parameter isn't part of the RangeQuery type. Without the correct user and sharingOptions parameters, the query builder fell into a "WHERE 1 = 0" clause, returning zero results every time. Agents checking for executions would find nothing, causing loops.

Workflow previews now load correctly even when the workflow name isn't returned in the tool call response—they fall back to the workflow ID, then enrich from the store to show the real name. Inline artifact cards in chat messages were also fixed to resolve names from the enriched registry rather than stale extracted names.

The Instance AI settings page now requires instanceAi:manage permission and is hidden from unauthorized users.

View Original GitHub Description

Summary

  • When the AI service proxy is enabled (license + N8N_AI_ASSISTANT_BASE_URL), the Model, Search, and Sandbox settings sections are hidden from the UI and their fields are stripped from update requests. When the proxy is not configured, all settings remain visible and functional.
  • Fix bug where preview does not load if workflow name not returned in tool call. Fall back to 'workflowId' when workflowId is present without a name. Then enrich from the workflow store via a workflowNameLookup callback so all consumers see the real name Also fixed the inline artifact card in chat messages (AgentTimeline) to resolve names from the enriched registry
  • The execution adapter was passing accessibleWorkflowIds to findManyByRangeQuery, but that field is not part of ExecutionSummaries.RangeQuery. Without user/sharingOptions, the query builder fell into WHERE 1 = 0, returning zero results every time — causing the agent to loop on "Checking executions" without finding anything.
<!-- Describe what the PR does and how to test. Photos and videos are recommended. -->

Related Linear tickets, Github issues, and Community forum posts

<!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/ --> <!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. -->

Review / Merge checklist

  • PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
  • Docs updated or follow-up ticket created.
  • Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
  • PR Labeled with Backport to Beta, Backport to Stable, or Backport to v1 (if the PR is an urgent fix that needs to be backported)
© 2026 · via Gitpulse