Job flow 5 · task:subscription-price-push Diagram

What each step does

Queued by plan-price-push. Job ID price-push-<plan>-<sub>-<price>; concurrency 5; attempts 5 with backoff.
Still applies: status ACTIVE, PAST_DUE, PENDING_REAUTH or PENDING_SETUP; same plan, asset count and interval the push was priced for (a plan change since then priced itself); not already staged and notified at this price.
Stage: pendingPriceAmount = new price; pendingPriceFromCycle = the next renewal if it is more than 24 hours away, otherwise the renewal after it (PENDING_SETUP → cycle 1, the first renewal after activation); pendingDiscountAmountPerCycle = running discount on the new price (percentage recomputed, fixed kept); priceUpdateNotifiedAt cleared.
Email 'Subscription Price Update Notification': old and new price per cycle, the renewal date it is first charged, 'Your running discount continues…' when one runs, and for Razorpay above the mandate 'You will be asked to re-authorize it before this renewal'. A failed send throws; the job is retried.
Record: priceUpdateNotifiedAt = time of the email; pendingPriceFromCycle moved one renewal later if the email went out less than 24 hours before the staged renewal. Until this is set the new price is never charged.
At renewal: the cycle is charged at the new price less the running discount; on success lockedPriceAmount and discountAmountPerCycle take the new values and priceUpdateAppliedAt is set. Razorpay with the new price above mandateMaxAmount → PENDING_REAUTH, no charge, re-authorization needed. Any plan change clears the pushed price.