Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update deprecated instructions #1

Open
Geczy opened this issue Dec 29, 2024 · 0 comments
Open

update deprecated instructions #1

Geczy opened this issue Dec 29, 2024 · 0 comments
Assignees

Comments

@Geczy
Copy link

Geczy commented Dec 29, 2024

WARNING: This node will not work properly for concurrent executions. It will only throttle sequential executions. It is recommended to set N8N EXECUTIONS_PROCESS mode to "main", so all executions will be sequential.

1.27.0

What changed?

The execution mode own was removed.
If EXECUTIONS_PROCESS is set to main or if executions.process in a config file is set to main n8n will print a warning, but start up normally.
If EXECUTIONS_PROCESS is set to own or if executions.process in a config file is set to own n8n will print an error message and refuse to start up.

When is action necessary?

If you use own mode and need the isolation and performance gains, please consider using queue mode instead, otherwise switch to main mode by removing the environment variable or config field.
If you have the environment variable EXECUTIONS_PROCESS or the config field executions.process set, please remove them. The environment variable has no effect anymore and the configuration field will be removed in future releases, prevent n8n from starting if it is still set.

@umanamente umanamente self-assigned this Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants