Job flow 4 · task:plan-price-push Diagram

Queued by: a super admin saving changed plan prices and choosing 'New and existing customers' (PUT /plan/plans/:id with applyToExisting), or 'Push new price to these' in Plan Details (POST /plan/plans/:id/price-push). No fixed job ID; attempts 5, exponential backoff from 5 s.
List: subscriptions of this plan in ACTIVE, PAST_DUE, PENDING_REAUTH or PENDING_SETUP with a locked price and a provider. A free plan has nothing to push.
Price differs: the plan rate for the subscription's own currency, interval and asset count, compared with what it pays now (pendingPriceAmount if one is staged, else lockedPriceAmount). Equal → left alone.
Gateway pair: getSubscriptionBilling must accept the stored company country and gateway; a mismatch is written to the job log as not pushed.
Add one job each: one task:subscription-price-push per subscription in a single addBulk, job ID price-push-<plan>-<sub>-<price> (a repeat of the same push adds nothing). The preview endpoint uses the same comparison to count subscriptions and Razorpay re-authorizations before the admin confirms.