Add warning that hashing detection applies only to action-destinations #7776
Conversation
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
harsh-joshi99
requested review from
pwseg and
Copilot
and removed request for
pwseg
There was a problem hiding this comment.
Pull Request Overview
This PR adds clarification to the documentation about hash detection functionality, specifying that it only applies to Action Destinations and not Classic Destinations. This change addresses user confusion about the scope of the automatic hash detection feature.
- Adds a warning callout to explicitly state that hashing detection is limited to Action Destinations
- Improves documentation clarity to prevent misunderstandings about feature availability
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
Slack Thread: https://twilio.slack.com/archives/CC97A542H/p1752733655757679
The previous documentation on pre-hash detection was causing confusion about whether this feature also applies to Classic Destinations.
This PR updates the wording to make it explicit that automatic hash detection is supported only for Action Destinations.
Merge timing