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.

Sign up for GitHub

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

Jump to bottom

Handle Slack::Notifier::APIError exception for multiple users #103

Closed
sushil-bsmarter opened this issue May 23, 2019 · 2 comments
Closed

Handle Slack::Notifier::APIError exception for multiple users #103

sushil-bsmarter opened this issue May 23, 2019 · 2 comments
Labels
enhancement released
Milestone
v2.1.0

Comments

@sushil-bsmarter
Copy link

sushil-bsmarter commented May 23, 2019 •
edited
Loading

I have added the slack as an optional targets and got slack working to send notifications to individual users. My use case is once an admin creates an event, the notification gets sent to all the users.

However, once a user slack notification does not work and the application encounters Slack::Notifier::APIError, it stops sending notification to remaining users. How can I continue to send notification to remaining users even if it fails for some? Please help.
@sushil-bsmarter sushil-bsmarter changed the title Handle Slack::Notifier::APIError exception Handle Slack::Notifier::APIError exception for multiple users May 23, 2019
@simukappu
Copy link
Owner

Prioritized. Error at optional target function will be rescued in the next minor version.

simukappu added a commit that referenced this issue Aug 13, 2019
@simukappu
Rescue and skip error in optional_targets - #103
3601402
simukappu added a commit that referenced this issue Aug 13, 2019
@simukappu
Rescue and skip error in optional_targets - #103
02c96ad
simukappu added a commit that referenced this issue Aug 13, 2019
@simukappu
Rescue and skip error in optional_targets - #103
b25e230
@simukappu simukappu added this to the v2.1.0 milestone Oct 12, 2019
@simukappu
Copy link
Owner

Released as v2.1.0. Thanks!

This was referenced Feb 9, 2021
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement released
Projects
None yet
Milestone
v2.1.0
Development

No branches or pull requests
2 participants
@simukappu @sushil-bsmarter