n8n 2.47.3 Fixes Migration Finding Ownership and Stale Task Cleanup
n8n 2.47.3 tightens who can own migration findings, cleans up stale scheduled tasks, and links notification emails to filtered reports.
n8n published version 2.47.3 on November 9, 2026. The patch release includes two bug fixes and one feature update, all focused on migration findings and scheduled tasks.
The first fix limits ownership of migration findings. Only users who can edit a workflow can now own that workflow’s migration findings. The second fix changes how stale scheduled tasks are cleaned up. Stale tasks are now retired in repeated batches during each reaper pass.
The feature update changes how migration reports open from notification emails. The migration report now opens filtered to the recipient who received the email, so people can go straight to the findings meant for them.
Why it matters
Migration findings are tied to specific workflows, so tighter ownership rules help teams keep control over who acts on them. Cleaner handling of stale scheduled tasks reduces leftover clutter in automation setups. The filtered email link saves recipients from searching for their own findings in a full report.
What to do
Teams that use migration reports should confirm who has edit access to each workflow, since that now determines who can own its findings. Review the full release notes on GitHub before upgrading. Check n8n’s website for upgrade steps and any compatibility details, because the release notes do not cover them.
In this story
Compare the tools in this story
The Stack Brief
Get the weekly brief
One email a week: SaaS pricing changes, launches worth knowing about, and one comparison you can act on.

Comments
Join the discussion with your GitHub account. Be civil, stay on topic.