# How do you catch silent push failures and escaping issues in SuprSend?

I like that SuprSend keeps APNs/FCM credentials on the server, so when a credential is wrong I can swap it on the SuprSend side and pushes start arriving within minutes, with no rebuild or store review. It also helps to see which Firebase project a credential belongs to and to fix a template once for every app. What’s been frustrating is when failures don’t announce themselves, like HTML-escaped push text showing "&" on device, or a Firebase project being shut down and failing quietly. How are you monitoring for these issues, and what checks or hints would you want (especially across workspaces)?

##### Post Metadata
- Posted at: 16 days ago
- Author title: Technical Solutions Engineer
- Net upvotes: 1



## Related Product
[SuprSend](https://www.g2.com/products/suprsend/reviews)

## Related Category
[Notification Infrastructure](https://www.g2.com/categories/notification-infrastructure)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4