Create section : Frequently asked questions #4005
Merged
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
Added relevant details for excessive notifications for audience/trait failures
|
@lizkane222 does this work still need to be done? It's quite old. We plan to close this PR on Friday, January26, 2024. |
|
Ready for review per Liz |
grammar
cmastr
approved these changes
Feb 21, 2024
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Closed
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.
Added relevant details for excessive notifications for audience/trait failures
Proposed changes
These excessive failures can be confusing to customers who might lose confidence in the product when finding contradictions within the UI between the Audit Trail which states failures and the audiences/traits that state successes. The additional FAQ section I've added provides a simplified explanation as well as a more in-depth internal processes explanation, as well as what they can do to resolve this excessive notifications => reach out to support.
Merge timing
Related issues (optional)
**Ref’d Zendesk tickets : **
https://segment.zendesk.com/agent/tickets/493355
https://segment.zendesk.com/agent/tickets/483136
https://segment.zendesk.com/agent/tickets/470175
The Support Workaround
Reducing notifications can be done through the use of the audit-log-failure / reduced-notifications-allow-list flag in Retool/Flagon.
You will need to add the Workspace ID here : https://retool.segment.com/apps/flagon/flag?family=audit-log-failure&filter=audit-&name=reduced-notifications-allow-list#family=&filter=audit-&name=.
Additional Internal Docs :
Personas Excessive Compute/Sync Failure Notifications in Audit Trail : This doc is around customers receiving notifications for Audience/Computed Traits failing runs/syncs, even though the UI shows successful runs/syncs when you look at the computation in their Personas space.
Audit Log Failure Notifications