Document error status codes returned for interactive message integrations#1507
Document error status codes returned for interactive message integrations#1507sbishel wants to merge 1 commit into
Conversation
|
Newest code from mattermost has been published to preview environment for Git SHA 48da468 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates the interactive messages plugin documentation to clarify error handling behaviour. The "Error handling" section reference is revised to match updated FAQ phrasing, and the FAQ entry is expanded to explicitly document how Mattermost maps integration/connectivity errors and invalid responses to HTTP status codes returned to clients. ChangesInteractive Message Error Handling Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Updates the interactive messages docs to reflect that Mattermost now preserves certain upstream HTTP status codes (rather than always returning 400) when an integration backing a button or menu fails, so API clients can honor retry semantics.
Related PRs
mattermost/mattermost#36700