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

Alerts processed for unlicensed users #13

Closed
mcoles opened this issue Feb 8, 2016 · 1 comment
Closed

Alerts processed for unlicensed users #13

mcoles opened this issue Feb 8, 2016 · 1 comment
Labels

Comments

@mcoles
Copy link
Contributor

mcoles commented Feb 8, 2016

VizAlerts will still attempt to process an alert based on an Unlicensed user who is still subscribed to a view on an Alerts schedule. This causes a failure email to be sent, because Tableau Server will refuse to provide the CSV data for a view on behalf of an unlicensed user.

My thought is that the correct behavior should be the same as standard Subscriptions functionality, which is that any Subscriptions for an unlicensed user are simply ignored. We could just exclude that data in the SQL query in the config file, but it'd be better to set a flag for those rows then have VizAlerts skip them but log that it did so. That way there's more visibility for the Admin on what's going on.

@mcoles mcoles added the bug label Feb 8, 2016
@mcoles
Copy link
Contributor Author

mcoles commented Apr 6, 2016

Improved this behavior such that now, if an alert is slated to be tested when the subscriber is unlicensed in Tableau Server, the alert will be skipped, but an email will be sent to the admin / subscriber with a clear reason for the error.

@mcoles mcoles closed this as completed Apr 6, 2016
mcoles added a commit that referenced this issue Apr 6, 2016
Improved this behavior such that now, if an alert is slated to be tested
when the subscriber is unlicensed in Tableau Server, the alert will be
skipped, but an email will be sent to the admin / subscriber with a
clear reason for the error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant