Skip to content

Commit 12a51c0

Browse files
estgclizkane222
andauthored
Add FAQ about failure notifications for audience and trait syncs (#4261)
* excessive notifications for aud/trait failures Added relevant details for excessive notifications for audience/trait failures * Update faqs.md --------- Co-authored-by: Liz Kane <[email protected]>
1 parent c8e9f72 commit 12a51c0

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

src/engage/faqs.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,3 +110,10 @@ The following list shows just some data sources you can sync to Engage:
110110
## Can I send audiences to multiple destination accounts?
111111

112112
Yes, Engage supports the ability to send an audience or computed trait to two or more accounts of the same partner. The most common use case is multiple Facebook, or Adwords ad accounts.
113+
114+
115+
### Why am I getting alerts about an audience/computed trait sync failure, but when I look at the specific audience/computed trait it shows a successful sync?
116+
117+
An audience/computed trait Run or a Sync may fail on its first attempt, but Engage will retry up to 5 times before considering it a hard failure and display on that audience/compute trait's Overview page. As long as the runs/syncs within the specific Audience's Overview page say they are successful, then these can be safely ignored. The Audit Trail logic, however, is configured in the way that it simply notifies about every task failure, even if it then later succeeds.
118+
119+
If your team would like to avoid receiving the notifications for transient failures, please **[reach out to support](https://segment.com/help/contact/)**, who upon request can disable transient failure notifications.

0 commit comments

Comments
 (0)