-
Notifications
You must be signed in to change notification settings - Fork 8
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
reloadTaskAborted and reloadTaskAborted recipients empty lists #640
Comments
Same with empty excludeOwner
|
Long overdue, a fix for this is coming in next version of Butler. The workaround would be to disable (in the YAML config file) the features causing problems, but it's of course better that Butler itself is resilient and deals with empty recipient lists in a good way. |
This was referenced Aug 21, 2023
This was referenced Dec 7, 2023
This was referenced Feb 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Butler are you using?
8.6.2
What version of Node.js are you using? Not applicable if you use the standalone version of Butler.
No response
What command did you use to start Butler?
/opt/butler-v8.6.2/butler --configfile ./config/production.yaml
What operating system are you using?
Debian 11
What CPU architecture are you using?
x86_64
What Qlik Sense versions are you using?
2022-November sp13
Describe the Bug
When in config sections I use empty recipients lists
I receive error
Expected Behavior
No response
To Reproduce
No response
The text was updated successfully, but these errors were encountered: