docs: blockedReason is operator-only, not returned via customer API#24
Open
tuyakhov wants to merge 1 commit into
Open
docs: blockedReason is operator-only, not returned via customer API#24tuyakhov wants to merge 1 commit into
tuyakhov wants to merge 1 commit into
Conversation
senderkit-app #211 removed blockedReason from all customer-facing message projections (messages.list, messages.get, SSE tail, logs page). Customers see only a generic "Blocked by automated content safety checks." timeline entry; the detailed detection signal breakdown is operator-only. The June 17 changelog entry and the SDK/concepts docs incorrectly described blockedReason as a customer-visible field with meaningful content — corrected across all three files. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L1Vn6uVk4YTQShZyH8j6oi
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
One doc-worthy change since the last run (June 17): senderkit-app #211 removed
blockedReasonfrom all customer-facing message projections. The June 17 changelog entry and two other pages incorrectly describedblockedReasonas a customer-visible field with meaningful content.Changes
changelog.mdx— Adds a June 19 entry clarifying thatblockedReasonis operator-only. Corrects the June 17 entry (removes theblockedReasondescription; replaces it with a note pointing to the June 19 correction).sdks/typescript.mdx— Fixes the<Note>aboutblockedstatus: removes the claim thatblockedReasonexplains the flag to customers; states instead that a generic timeline notice is what customers see.concepts/messages.mdx— Fixes theblockedrow in the lifecycle table: removes "TheblockedReasonfield explains why" and replaces with "The message timeline records a generic notice; detection details are operator-only."What changed in the product (senderkit-app #211)
lib/services/messages.tsnow exports amessageColumnsprojection that explicitly excludesblockedReasonfrom every customer-facing read (API list, API get, SSE tail, logs-page SSR). The customer-visible blocked timeline entry is"Blocked by automated content safety checks."The field value (credential_form: …,llm_suspicious: …, etc.) stays in the DB and the admin abuse console only.PRs reviewed (since June 17)
🤖 Generated with Claude Code
https://claude.ai/code/session_01L1Vn6uVk4YTQShZyH8j6oi
Generated by Claude Code