Before changing a rep's workflow, check the undo window, action log retention and enrollment history retention.
Key takeaways
- Before you touch a live workflow, write down its current triggers, re-enrollment settings, unenrollment settings, actions, and delays.
- In HubSpot, undo and redo cover only recent edits, so do not assume you can roll back an older change.
- Save or export action log data before its retention period ends, because the log does not promise to stay available after that.
A trigger gets a new condition, a delay gets shorter, or a re-enrollment setting gets switched on. Then a question comes up a few weeks later. Why did a contact get that email? When did the change happen? Can we go back to the old version?
The answers depend on what the software keeps and for how long. Before you touch a live workflow, it helps to know three things: how far back you can undo or redo edits, how long the action log is stored, and how long enrollment history is kept. This post uses HubSpot's workflow documentation as the example, because it states a specific limit for each of these. Your tool may have different limits, and you should check its documentation before you rely on any of them.
This is a practical guide, not legal or compliance advice. If your company has record-keeping requirements, ask the people who own them, and let them decide how long your team keeps its own records.
Rule 1: In HubSpot, you can undo or redo edits made in the previous 30 days
In HubSpot, you can undo or redo changes to a workflow that were made in the previous 30 days. HubSpot's Create workflows article says this applies "when editing your workflow."
Do not treat the window as a promise about older changes or how many steps you can undo. Do not assume you can roll back a change from six weeks ago just because the editor has an undo button.
The window also moves while the workflow is live. A workflow that you changed on the first of the month has less time left to undo on the fifteenth than it had on the second. If a rep's workflow was changed in a way that needs reversing, the safest time to do it is while the change is still inside the undo window. After that, you should plan to rebuild the old version by hand from your notes or a saved record. The later section on writing down settings explains what that record should contain.
Rule 2: In HubSpot, action log data is stored for 90 days
In HubSpot, all workflow action log data is stored for 90 days. The Create workflows article describes this retention period.
The log includes object ID, event type and action type. In practice, they tell you which record an action touched, what kind of event happened, such as an enrollment or an unenrollment, and which action was involved.
That is useful when you are checking what a workflow did. It is less useful when you are trying to answer a question about something older than 90 days. Do not plan around the log being available beyond its retention period.
The two windows answer different questions. The undo window is for reversing an edit. The action log window is for reviewing what the workflow did. If a rep reports a problem with a follow-up sequence, pull the action log while it is still within the 90-day period. Export or save anything you need before it ages out, and do not wait for the rep's next report to start looking.
Rule 3: In HubSpot, enrollment history is kept for 2 years or more
In HubSpot, historical enrollment data is retained for 2 years or more. The Create workflows article says this data is "retained in our system to enable workflow-based filters."
Notice what this rule covers and what it does not. It covers historical data of enrollments. The article states the purpose of keeping that data as workflow-based filters. Do not treat enrollment retention as a way to restore a workflow.
Why does this matter when you edit a workflow? Enrollment history is the record most closely tied to who entered a workflow. The enrollment retention period is longer than the action log retention period. Keep its filtering purpose separate from reviewing individual actions.
These are different windows for different things. Treat them as separate limits, not as one retention period. A manager who remembers only one of them will be surprised by the others.
Before you edit, write down the current settings
Write down the current settings before you change anything. The undo window is short, so do not count on it as your only record of how the workflow used to work.
Your note should include the enrollment triggers, the re-enrollment settings, the unenrollment settings, the actions in order, and the delays between them. Add the date of the edit, the name of the rep or team the workflow serves, and the reason for the change. A screenshot of the editor is also helpful if your team uses one. If someone else will look at the workflow later, write the note so that person does not need to ask you what you meant.
For related record checks, see sales coaching logs.
This note is your own record. If it is missing, you are relying on the undo window, which the documentation limits to the previous 30 days. A missing note also means you have to reconstruct the old version from memory, and memory is a poor source when a rep is asking why a contact received a message.
Then decide who will check the workflow after the change. A changed workflow that runs for a week before anyone looks at it has used part of the time you had to undo it. Set a review date on the calendar before you publish, and make it fall inside the 30-day window so you still have the option to undo. If the review finds a problem, you can act while the edit is still reversible.
What to do with the editing steps
HubSpot's guide describes the editing steps in its Create workflows article. Two of the steps matter for this decision. The article says that in the workflow editor, you "add enrollment triggers and configure re-enrollment and unenrollment settings." It also says that you should "finally, configure your workflow settings, then turn on and publish your workflow."
Those steps are where the risk sits. Enrollment triggers control who enters the workflow. Re-enrollment and unenrollment settings control when contacts can enter again or leave. Publishing puts the change into effect. If you change any of these, the results may be recorded in the enrollment history and the action log, which is why the retention windows above matter.
The quoted steps describe building and turning on a workflow. Use your own team's rules for reviewing and approving a change to a rep's workflow. Write them down so that a manager who was not in the room can follow them. A short approval step, such as a second person reading the note before publishing, costs little and gives the next person a clear place to look.
A simple checklist for managers
Use this list before you edit a rep's follow-up workflow:
- Note the current triggers, re-enrollment settings, unenrollment settings, actions, and delays.
- Confirm the change is needed and say why in your notes.
- Review an existing edit and, if necessary, undo or redo it within 30 days after making it.
- Turn on and publish the workflow only after you have your notes saved.
- Save or export any action log data you may need before the 90-day period ends.
- Treat retained enrollment data as support for workflow-based filters.
- Set a review date that falls inside the 30-day undo window.
Illustrative example: Schedule the review
In an illustrative workflow change, a manager saves the old settings, changes a delay and schedules a review 10 days later. At the review, the manager checks what happened and decides whether to keep or undo the edit.
Why this matters for rep workflows
A rep's follow-up workflow is a set of messages to real people. A prospect who gets an email at the wrong time, or who gets enrolled twice, can be frustrated, and the rep may have to explain what happened. When that happens, the first thing a manager needs is a clear account of what changed. The retention limits decide how much of that account the software can still show you.
This is not a reason to avoid editing workflows. Teams need to change them as their process changes. It is a reason to edit with the records in view. If you know the undo window is 30 days, you will not wait until the change has been live for two months to decide you want it reversed. If you know the action log covers 90 days, you will pull the log while the question is fresh. Keep enrollment data's filtering purpose separate from results reporting.
Managers may want a single rule that applies to every tool. There is not one, and this post does not offer one. Each platform sets its own limits, and each one may change them. HubSpot's documentation is specific about its own windows, and those are the only retention numbers in this post that come from a source. For any other tool, find its documentation, read what it says about retention, and write the limits down in the same format as the three rules above.
Keep your own record
The software's history is useful, but it should not be your only record. The undo window is short. The action log has a fixed retention period. The enrollment history is kept for a longer period, and the documentation gives filtering as the reason for keeping it.
Your own record can be simple. A shared document with a dated entry for each workflow change works well. Include the old settings, the new settings, the reason, and the person who approved it. Store the document where the people who need it can find it, and keep it for as long as your team's own rules require. When a question comes up later, you will have an answer that does not depend on any single retention window.
For a related recovery check, see getting back an old coaching document version.
Make record-keeping part of each edit. It can save a lot of effort when something goes wrong, and it makes it easier to explain a change to a rep, to a colleague, or to yourself when you look back at it months later.
What to do today
Choose the next workflow you plan to change and write down its current settings before editing it. Set a review date inside the undo window, so you can still reverse the change if the review finds a problem.
Questions before you edit
Can enrollment history restore a workflow?
Do not rely on enrollment history to restore a workflow; keep your own record of its settings.
What should you check in another tool?
Check its documentation for undo, action log and enrollment retention limits before your next edit.
You can read the source for these rules in HubSpot's Create workflows article. If you use a different tool, look up its limits and write them down before your next edit.