Production Checklist Regression Since [email protected] — always shows 0/2 even when settings are configured

Questions
1

Hi team,

I wanted to flag a regression in the Production Checklist that’s been present since n8n 2.11.0 (March 3, 2026). The checklist always displays 0/2. Both “Set up error notifications” and “Track time saved” appear unchecked, even when those settings are properly configured in the workflow. The settings themselves still work correctly (error workflows still trigger, time saved still tracks), but the visual indicator is always wrong until a full page reload.

I see that #27268 was filed by another community member reporting the same issue, and PR #27246 has an open fix. I wanted to add some context on the root cause and timeline that might help prioritize the merge.

Root cause

PR #26407 (“Migrate settings to normalized workflow document state”) was merged on March 3. This refactored WorkflowSettings.vue to save settings to the new workflowDocumentStore instead of the previous workflowsStore.workflowSettings path. However, WorkflowProductionChecklist.vue was not updated in the same PR; it continued reading completion state from props.workflow.settings, which is now a stale snapshot that never reflects saves.

In short, the write side was migrated to the new store, but the read side (the checklist) was left on the old path.

Timeline

  • March 3 — PR #26407 merged, breaking the checklist
  • March 3 — [email protected] (prerelease) ships with the regression
  • March 9 — [email protected] (first stable release with the regression)
  • March 19 — Issue #27268 filed by community member
  • Current — [email protected] (latest stable) still affected
  • Fix — PR #27246 is open but not yet merged

Impact

While the bug is cosmetic (the underlying error workflow and time saved features still function), it creates confusion for users who rely on the checklist to verify their workflows are production-ready. It also undermines trust in the UI; users may not realize the settings are actually working and could waste time re-configuring them.

Suggestion for the future

This type of regression, where a refactor migrates one side of a read/write pair but misses the other, is a common pattern during store migrations. One approach that could help catch these earlier would be adding a simple integration test that verifies the end-to-end flow: save settings via the Settings modal, then assert that the Production Checklist reflects the updated state without a page reload. PR #27246 actually includes a test like this (should mark time saved as completed when timeSavedPerExecution is in workflowDocumentStore but not in props.workflow.settings), which would have caught the regression if it had existed before the migration.

Would it be possible to prioritize merging PR #27246? It’s a clean fix with good test coverage, and the regression has been in stable releases for about three weeks now.

Thanks for all the work on the document store migration; it’s a big architectural improvement. Just want to make sure this gap gets closed. Thanks!

2

Thanks for the detailed bug report and root cause analysis! You’ve clearly identified the issue — the checklist read-side wasn’t updated when the write-side migrated to the new store. PR #27246 looks like the right fix. This type of regression is worth prioritizing.

3

Hi @Darien_Kindlund
I think this is better suited for GitHub than the forum.
Since there is already an open issue and a PR for the same regression, I’d add this context directly to the existing GitHub thread so the engineering team can track it in one place. The forum is useful for support and community discussion, but for a reproducible UI regression with an identified issue and fix in progress, GitHub is usually the better home.

4

@tamy.santos , I’m calling it out on this forum because:

  1. This is a usability issue and glaring for any n8n user.
  2. This issue/PR has been open for 3+ weeks and still has not been resolved.
5

@Darien_Kindlund
In that case, I suggest submitting this under the Known Issues category: Known Issues - n8n Community
This will make the report more accurate and improve the chances of it being addressed by the n8n team.

6

I registered to echo my frustration with this issue. I really appreciated reading the background post here, the regression has kinda been driving me nuts for some reason.

That said, super appreciate the hard work of everyone involved. :slight_smile:

7

Hi @tamy.santos , I tried to move this post over to Known Issues but the front end UI doesn’t seem to allow me to do that when I try editing the post:

image
image570×260 11.5 KB

8

@Darien_Kindlund
Hey! Since this is a different topic, it’s probably best to close this thread and post a new one over here: Known Issues - n8n Community. That way, we can keep the discussions organized and easier for others to find!