#StackBounty: #graphql #amazon-dynamodb #react-apollo #aws-amplify #aws-appsync How does AppSync subscriptions handle resolver exceptio…

Bounty: 50

I’ve noticed that throwing an exception in my subscription response mapping template results in the subscription not reaching the client.

I am building a chat feature and need to ensure new messages are delivered to client devices consistently. What happens if there is throttling exception (as a result of not provisioning enough RCU for example)? The client will be unaware that a new message unsuccessfully attempted to reach them.

Is there a way to retry the subscription, or at least inform the client so that they can pull new messages after a backoff period?

Get this bounty!!!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.