frugal
frugal copied to clipboard
Add actual values to uncommon exceptions
Story:
Need more info to debug these rare occurrences.
Add actual values to uncommon exceptions (method name, type)
Acceptance Criteria:
- [ ] Code has been tested and results documented
- [ ] Unit tests have been updated
- [x] Updates to documentation if necessary
- [x] Verify and document changes to any other Messaging components
- [x] Pull request made against the 'develop' branch, not master
Design Notes:
TODO
How To Test:
TODO
My Test Results:
TODO
Reviewers:
@Workiva/service-platform
Security Insights
No security relevant content was detected by automated scans.
Action Items
- Review PR for security impact; comment "security review required" if needed or unsure
- Verify
aviary.yaml
coverage of security relevant code
Questions or Comments? Reach out on Slack: #support-infosec.
Ok @Workiva/service-platform I really don't know why skynet is breaking now, help.