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

Don't fail when recurring tasks are defined for another environment #470

Merged
merged 1 commit into from
Dec 27, 2024

Conversation

rosa
Copy link
Member

@rosa rosa commented Dec 27, 2024

For example, production only, and the configuration is being loaded for development. In this case, we can't take the env key as the task definition, failing to load Solid Queue at all.

Fixes #468

For example, `production` only, and the configuration is being loaded
for `development`. In this case, we can't take the env key as the task
definition, failing to load Solid Queue at all.

Fixes #468
@rosa rosa merged commit c915561 into main Dec 27, 2024
8 checks passed
@rosa rosa deleted the fix-missing-envs-for-recurring-tasks branch December 27, 2024 16:58
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

Successfully merging this pull request may close these issues.

Upgrading to 1.1.1 makes recurring job to fail
1 participant