Iván Ovejero 4c4082503c feat(core): Coordinate manual workflow activation and deactivation in multi-main scenario (#7643) ... Followup to #7566 | Story: https://linear.app/n8n/issue/PAY-926 ### Manual workflow activation and deactivation In a multi-main scenario, if the user manually activates or deactivates a workflow, the process (whether leader or follower) that handles the PATCH request and updates its internal state should send a message into the command channel, so that all other main processes update their internal state accordingly: - Add to `ActiveWorkflows` if activating - Remove from `ActiveWorkflows` if deactivating - Remove and re-add to `ActiveWorkflows` if the update did not change activation status. After updating their internal state, if activating or deactivating, the recipient main processes should push a message to all connected frontends so that these can update their stores and so reflect the value in the UI. ### Workflow activation errors On failure to activate a workflow, the main instance should record the error in Redis - main instances should always pull activation errors from Redis in a multi-main scenario. ### Leadership change On leadership change... - The old leader should stop pruning and the new leader should start pruning. - The old leader should remove trigger- and poller-based workflows and the new leader should add them.		2023-11-17 15:58:50 +01:00
..
importCredentials	fix(core): Fix data decryption on credentials import (#7560)	2023-10-31 13:15:09 +01:00
importWorkflows	fix(core): Deactivate active workflows during import (#5840)	2023-03-30 15:33:30 +02:00
credentials.cmd.test.ts	ci(core): Reduce memory usage in tests (part-2) (no-changelog) (#7671)	2023-11-10 15:04:26 +01:00
import.cmd.test.ts	ci(core): Reduce memory usage in tests (part-2) (no-changelog) (#7671)	2023-11-10 15:04:26 +01:00
reset.cmd.test.ts	ci(core): Reduce memory usage in tests (part-2) (no-changelog) (#7671)	2023-11-10 15:04:26 +01:00
worker.cmd.test.ts	feat(core): Coordinate manual workflow activation and deactivation in multi-main scenario (#7643)	2023-11-17 15:58:50 +01:00