Avoid using the same audience key twice, even if you've deleted the key's original audience. Downstream tools andDestinations might have trouble distinguishing between different audiences thatat any pointshared the same key.

Avoid using the same audience key twice, even if you've deleted the key's original audience. Downstream tools anddestinations might have trouble distinguishing between different audiences thatonceshared the same key. This may create mismatch in audience size between Segment and the destination because the destination may count users of the old audience, resulting in a larger audience size.

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.

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.