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

Butler checks for custom property Butler_SuccessAlertEnableEmail even though feature is disabled #1308

Open
mountaindude opened this issue Dec 3, 2024 · 1 comment

Comments

@mountaindude
Copy link
Collaborator

What version of Butler are you using?

13.1.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?

What operating system are you using?

What CPU architecture are you using?

What Qlik Sense versions are you using?

Describe the Bug

2024-12-03T10:26:19.099Z error: ASSERT CONFIG EMAIL: Custom property 'Butler_SuccessAlertEnableEmail' not found in Qlik Sense. Aborting.
2024-12-03T10:26:19.101Z error: MAIN: Config file does not contain required email data. Exiting.

But the use of a custom property for controlling sending of reload success emails is disabled in the config file, so the existence of the custom property should not be done:

 emailNotification:
    enable: true
    reloadTaskSuccess:
      enable: true
      # Custom property used to control which task successes will cause alert emails to be sent
      # If this setting is true, alerts will not be sent for all tasks, but *only* for tasks with the CP set to the enabledValue.
      # If this setting is false, alerts will be sent for all failed reload tasks.
      alertEnableByCustomProperty:
        enable: false
        customPropertyName: 'Butler_SuccessAlertEnableEmail'
        enabledValue: 'Yes'

Expected Behavior

No response

To Reproduce

No response

Copy link
Contributor

github-actions bot commented Jan 3, 2025

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant