Salesforce AppExchangeimplicitmediumCluster of 4 signals
Card #2609 · Salesforce AppExchange

Lack of pause/resume and status-based triggers for timers

Standard escalation rules and timers cannot be paused or resumed based on status changes, often resetting upon any field modification. Merchants need the ability to trigger status changes when timers start or enforce pause logic when cases are put on hold.

Salesforce AppExchangeUpdated 23d ago0.59
Pain score
0.59/ 1.00 · weighted product of four components
Reach0.47
distinct authors (log-normalized)
Recency1.00
freshness decay, half-life months
Engagement1.00
upvotes + comments, normalized
Monetization0.50
willingness-to-pay cues in evidence
§ Evidence — 4 verified quotes
an Escalation Rule alone is usually not enough because you need the timer to pause/resume based on status changes.
Reddit·@s2labs··source ↗
any field edit resets the timer with "last modification time," and you'd lose count even on unrelated updates.
Reddit·@Designer_Savings9375··source ↗
even AI Studio does not allow you to implement a status change when the timer starts.
Forum·@Olesia_Chegodaeva··source ↗
I’d love to use it as a trigger to change Custom Field Status to “In Progress” once Actual Time timer is started.
Forum·@Robert_Gallagher··source ↗

Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.

Upgrade to Pro