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

Retry failed notifications #7

Open
JamesHemery opened this issue Dec 12, 2022 · 0 comments
Open

Retry failed notifications #7

JamesHemery opened this issue Dec 12, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@JamesHemery
Copy link
Member

It would be nice to implement a retry (exponential backoff) system for failed batched notifications.

For non-batched notifications, it would be necessary to throw an exception or dispatch an event when the notification fails.

We talk about a failed notification when the payload is valid but Expo returns with a error status.

When the payload is invalid, Expo returns a body containing errors field and the Service throw an ExpoNotificationsException.

Also, we could consider dispatching an event when a Ticket or Receipt is in error status.

@JamesHemery JamesHemery added the enhancement New feature or request label Dec 12, 2022
@JamesHemery JamesHemery self-assigned this May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant