Update actions.md Added comprehensive migration strategy #4807
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
Walkthrough provided for a comprehensive classic/actions migration strategy
cmastr
reviewed
Jan 25, 2024
forstisabella
requested changes
Jan 26, 2024
Review items added. Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com>
cmastr
approved these changes
Jan 31, 2024
forstisabella
approved these changes
Jan 31, 2024
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
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.
Walkthrough provided for a comprehensive classic/actions migration strategy
Proposed changes
Many customers have inquired about ensuring that their events are not dropped or duplicated when migrating from a Classic to Actions destination. The existing steps provided are useful and applicable to all non-BT customers, while the comprehensive guide I've shared is available to BT customers who want to ensure all events are successfully sent to the destination, none getting dropped or duplicated.
Merge timing
Related issues (optional)
Zendesk Tickets :
Mark Zegarelli: here's one of the charts we discussed that might be useful to share at this point, after getting redesigned of course :
Migrate from Classic to Actions Destination.pdf