The idea is:
Allow the n8n AI Builder to continue running in the background even if the user refreshes the page, leaves the editor, or navigates to another workflow. The AI Builder job should persist server-side and resume or surface its result when the user returns, instead of stopping execution.
My use case:
When building workflows with the AI Builder, I often trigger it and then switch to another workflow, refresh the page, or accidentally navigate away. Currently, this immediately stops the AI Builder process and consumes credits without producing a result. This breaks the flow when multitasking or working on multiple workflows in parallel.
I think it would be beneficial to add this because:
- It prevents wasted AI credits when users leave or refresh the page.
- It improves reliability and trust in the AI Builder.
- It enables better multitasking and longer-running AI build processes.
- It aligns the AI Builder experience with background jobs already common in automation tools.
Any resources to support this?
No external resources, but this behavior is similar to background job handling in other AI-assisted tools where tasks continue running independently of the UI session.
Are you willing to work on this?
Not at the moment, but I’m happy to help test, provide feedback, or clarify requirements if needed.