Problem with automation when a product is purchased again – how to prevent issues?
Here's how my automation currently works:
- WooCommerce assigns a tag after a successful purchase.
- This tag triggers an automation in FluentCRM.
- The automation grants access to a course (BuddyBoss/TutorLMS), sends emails, etc.
- After 30 days, the tag is removed, access is revoked, and the user receives a notification about the end of access.
The problem arises when a user purchases the same product again before the 30-day period ends:
- The new purchase does not assign the tag (because it already exists), so the new automation doesn’t start.
- Meanwhile, the old automation still removes access after 30 days, even though the user just paid again.
Has anyone encountered a similar issue and found a way to prevent this kind of conflict between overlapping purchase cycles?
Instead of tag based automation trigger, start the automation directly from the WooCommerce purchase trigger in FluentCRM Automation. Then enable restart automation Multiple Times. In this way, the issue will be resolved.
Shahjahan Jewel If I understand correctly, in such a case, if there’s already an existing automation running for the client, it gets canceled and replaced with a new one at the moment of purchase?
Michal Paczula that’s correct.