Basically, I would like to create a flow to remove a certain tag when it reaches 24 hrs after it has been added. Does anyone know how to do that?
Yes
Please clarify in which specific object you want to delete the tag after 24 hours: order, customer, or product?
Hello @TiffanyChung ,
Can you please provide more details? (Like when it will trigger or how the tag will be added? It is possible to create the flow using Shopify flow. Acccording to my understanding I have created the Workflow:
We currently have a Shopify Flow set up so that when a specific customer tag is added, our RIVO Loyalty app awards points to the customer, and then the tag is removed after the points have been added.
However, Iâd like to modify the flow so that the tag is removed 24 hours later, rather than immediately. I tried adding a âwait 24 hoursâ step before removing the tag, but during that waiting period, points continue to be added repeatedly.
Is there a way to ensure that:
- The tag is automatically removed 24 hours after itâs added to the customer account, and
- Points are only added once, not multiple times within that 24-hour window?
Hey @TiffanyChung,
I can see the issue with your current flow. The problem is that every time the flow triggers (when the tag is detected), it adds points AND queues up a tag removal for 24 hours later. So if the tag gets detected multiple times during those 24 hours, you get multiple point additions.
Here are a few solutions to fix this:
Solution 1: Add a âProcessingâ Tag (Recommended)
Modify your flow like this:
Current Flow Structure:
- Trigger: Customer tags added
- Check if: Customer state is ENABLED
- Check if: Tag equals â100 Pointsâ
- Add Points
- [ADD DELAY: 24 hours]
- Remove customer tags: â100 Pointsâ
Modified Flow Structure:
- Trigger: Customer tags added
- Check if: Customer state is ENABLED
- Check if: Tag equals â100 Pointsâ
- Check if: Customer tags does NOT contain â100-Points-Processingâ
- Add customer tag: â100-Points-Processingâ
- Add Points
- Delay: 24 hours
- Remove customer tags: â100 Points, 100-Points-Processingâ
This way, once the â100-Points-Processingâ tag is added, the flow wonât trigger again for the same customer until both tags are removed.
Solution 2: Use Multiple Flows
Flow 1 - Add Points (One-time)
- Trigger: Customer tags added
- Check if: Tag equals â100 Pointsâ
- Check if: Customer tags does NOT contain â100-Points-Processedâ
- Add customer tag: â100-Points-Processedâ
- Add Points
Flow 2 - Remove Tags (24hr delay)
- Trigger: Customer tags added
- Check if: Tag equals â100 Pointsâ
- Delay: 24 hours
- Check if: Customer still has â100 Pointsâ tag
- Remove customer tags: â100 Points, 100-Points-Processedâ
For Your Specific Flow in the Image (the one you shared):
Looking at your current setup, Iâd recommend Solution 1. Hereâs exactly what to modify:
For the â100 Pointsâ branch:
- After âTag is equal to 100 Pointsâ condition
- Add new condition: âCustomer tags does NOT contain â100-Points-Processingââ
- If TRUE: Add customer tag â100-Points-Processingâ â Add Points â Delay 24 hours â Remove tags â100 Points, 100-Points-Processingâ
- If FALSE: End (do nothing)
For the â250 Pointsâ branch:
- After âTag is equal to 250 Pointsâ condition
- Add new condition: âCustomer tags does NOT contain â250-Points-Processingââ
- If TRUE: Add customer tag â250-Points-Processingâ â Add Points â Delay 24 hours â Remove tags â250 Points, 250-Points-Processingâ
- If FALSE: End (do nothing)
For the â500 Pointsâ branch:
- Same logic with â500-Points-Processingâ
This ensures that:
- Points are only awarded once per tag application
- Tags are removed after exactly 24 hours
- No duplicate point awards during the waiting period
The key is using that âprocessingâ tag as a flag to prevent the flow from running multiple times for the same point award.
Let me know if you need help setting up any of these conditions!
Shubham | Untechnickle
Hey @TiffanyChung,
Yes, your 100 Points branch setup is absolutely correct!
Feel free to reach out if youâve any more questions for us, weâd love to help.
Cheers!
Shubham | Untechnickle