

Understand how Duration in Days fires actions every X days (exact multiples), and use it to keep pipelines clean by removing stale opportunities—plus a workaround for retroactive cleanup.
The legacy Triggers feature is deprecated in BizStackPro. For new automation setups, use Workflows with pipeline/opportunity events instead.
Sales pipelines can quickly become cluttered when inactive opportunities remain untouched for weeks, making it harder for teams to focus on leads that are still actively moving forward.
The Duration in Days filter inside BizStackPro Triggers allows businesses to automate actions based on inactivity intervals, such as removing stale opportunities or sending recurring follow-up reminders.
Without automated inactivity management, pipelines can become difficult to maintain, reporting may become inaccurate, and follow-up efforts can waste time on outdated opportunities.
This guide explains how Duration in Days logic works, how exact interval triggering behaves, how to remove stale opportunities automatically, and how to handle retroactive cleanup workflows inside BizStackPro.
Before building inactivity-based automation rules, it helps to understand how Duration in Days intervals, stale opportunity triggers, retroactive cleanup limitations, and tag-based workarounds function inside BizStackPro.
The Duration in Days filter fires once every X number of days when a contact or opportunity matches the criteria. The key detail: it triggers only on exact multiples of the duration.
Example: If X = 7, the trigger can fire at 7, 14, 21, 28… days of inactivity—not at 8 or 9 days.
This is commonly used to remove stale or inactive opportunities from a pipeline, but it also works well for recurring reminders, follow-ups, notifications, or cleanup routines.
Let’s say you want to remove opportunities when they become stale every 7 days.
John may be captured later when his last activity hits 14 days, 21 days, etc.
Heads up: The Stale Opportunities trigger does not apply retroactively to opportunities that existed before you created the trigger. The workaround below helps you clean up existing records.
For stale opportunity cleanup, add an action like:
You can also add notifications, tags, internal tasks, or other actions depending on your process.
Save and activate the trigger so it begins evaluating opportunities using your Duration in Days interval.
Because Duration in Days does not retroactively evaluate existing opportunities, this workaround lets you remove old stale opportunities that were already in your pipeline before the trigger was created.
Go to Settings → Tags and create a tag such as stale opp or stale opportunity.
Save and activate the trigger.
Result: Adding the tag fires the tag-based trigger and removes stale opportunities retroactively from the selected pipeline.
Use Duration-based logic to keep your pipeline focused on active opportunities—and use Workflows going forward for modern, reliable automation.
Opens in a new tab.
No. It fires only when inactivity matches an exact multiple (for example, 7, 14, 21 days).
Not retroactively. Use the tagging workaround in Part 2 to remove pre-existing stale opportunities.
Yes. You can use it for reminders, follow-ups, notifications, tagging, tasks, and other time-based automations.
No. Only future cycles are evaluated. Use the tagging method to retroactively clean up existing records.
Yes. You can configure different pipelines/stages with different durations for granular cleanup rules.
Duration-based automation helps you prune inactive opportunities, reduce clutter, and keep your team focused on leads that are still moving.
Cleaner pipeline. Better follow-up.
Disclaimer: This site is NOT endorsed by Google, Facebook or YouTube in ANY WAY. All trademarks & Logo / branding are the property of their respective owners. Please Note: This site was created in BizStackPro by Ken George II (An Affiliate of BizStackPro) and may contain affiliate links.

Copyrights 2024 | AllAboutBizStackPro.Com | Pricing | About | Features | All Rights Reserved.