I could have sworn there was a post about this sometime in the past, but here goes:
The use of the "Create CTA Once in X days" functionality when combined with the "Include in Identifiers" option creates a problem that has existed for a long time but still has no solution.
If a CSM edits the name of a CTA, it resets the “once in X Days” restriction that’s supposed to prevent duplicate CTAs. This means that after the name change, the system no longer treats the CTA as an existing one and will trigger a new CTA before the X-day window expires. This causes duplicate CTAs for the same task, cluttering workflows and creating confusion.
The only thing I can do as an admin is say “Please don’t change the name of the CTA, ok?” which is routinely ignored bc users either don’t pay attention to enablement half the time or go rogue.
Why this is problematic:
- Duplicate CTAs: Name changes bypass the X-day restriction, so you can end up with multiple CTAs for the same issue, adding unnecessary clutter.
- Inaccurate Reporting: Multiple CTAs skew reports and tracking, leading to data inconsistencies.
- Wasted Time: Admins or CSMs have to manually clean up these duplicates, defeating the purpose of automated workflows.
Isn’t there a backend value that correlates a triggered CTA to a specific action that can be used in the “X-days” evaluation instead of the CTA Name?
Or, at a minimum, give us an option in a rule action to “lock” the CTA Name from being edited for CTAs that are auto-triggered.
