Implemented
0
Workflow settings cannot unset callerIds after workflowsFromAList; exact restore is impossible
Source: n8n-io/n8n#40549 · opened by @Le-Serviteur
Bug Description On n8n Cloud, after temporarily setting a workflow to: there is no supported workflow-settings update path that restores the raw settings to a prior state where the callerIds key was completely absent. This is not an authorization-bypass report: restoring callerPolicy = none correctly blocks sub-workflow callers. The issue is exact rollback/state restoration. We use pre-mutation snapshots and require the post-restore raw workflow settings to match the pre-mutation state. If callerIds was absent before the temporary authorization, n8n currently leaves the old value persisted after restore. To Reproduce 1. Start with a workflow whose raw settings do not contain callerIds: Verify: 2. Temporarily set: 3. Restore the original settings object, intentionally omitting callerIds. 4. Read the workflow settings again. Observed: We also tested the available alternatives on disposable workflows: Expected behavior There should be a supported way to restore …
No pledges yet. Be the first to back this.
Comments
Similar requests
Feature: cross-workflow agent memory — persistent verified memory for AI Agent nodes
0 votes · 0 comments
Next scheduled workflow is executed before previous workflow has finished
0 votes · 0 comments
Feature: Add configurable request-body validation to the Webhook node
0 votes · 0 comments
SQLite database file never shrinks after execution pruning/deletion — disk fills up despite pruning being enabled
0 votes · 0 comments
Forced production checklist for workflows also doent work
0 votes · 0 comments
No comments yet.