Blockers and warnings

RevBridge separates dry-run findings into blockers and warnings.

Blockers stop automatic execution for a subscription. Warnings tell operators about behavior that may still be valid but should be reviewed.

Common blockers

Blockers include unsupported or unsafe cases such as:

• Missing customer mapping.
• No billing-relevant source subscriptions to evaluate.
• Destination customer already has a non-terminal subscription outside this RevBridge migration plan.
• Multi-item subscriptions whose items bill on different intervals or report different period ends.
• Manual invoice collection, custom cancel dates before the next renewal, thresholds, or pending subscription changes.
• Billing cycle anchor config.
• Outstanding latest invoice balances.
• Non-zero draft/open/uncollectible customer invoices in either account.
• Pending source invoice items on the customer or subscription.
• Pending destination invoice items on the customer or recovered destination subscription.
• Subscription presentment details or adaptive-presentment currency state.
• Unknown billing modes, unknown flexible billing configuration, or Connect transfer settings. Classic and flexible billing modes are both supported and mirrored.
• Custom subscription payment settings, including non-card payment method types, payment method options, non-off save-default behavior, or non-empty future payment setting fields RevBridge does not yet preserve. Explicit card-only payment_method_types is allowed.
• Custom subscription invoice settings.
• Customer-level invoice rendering settings.
• Metered prices.
• Unsupported interval or price structures.
• Subscription schedules.
• Paused subscriptions.
• Unsupported subscription statuses such as incomplete, past_due, or unpaid.
• Unsupported trial settings, including unknown missing-payment-method behavior values.
• Preserved renewal timestamp is missing or not in the future.
• Unsupported tax state, including Stripe Tax, customer tax settings/IDs, default tax rates, and item tax rates. Explicit price tax_behavior is supported.
• Promotion codes or unsupported discount shapes, including repeating coupons whose remaining window cannot be matched by a whole-month clone.
• Voided latest invoices that show a once coupon.
• Customer-level discounts in either account.
• Customer balance, invoice credit balance, or cash balance in either account.
• Missing destination payment method for a recurring subscription that can collect a future non-zero invoice.
• Ambiguous destination payment method match.
• Source customer without a usable payment method.

Common warnings

Warnings include reviewable fallbacks or non-fatal behavior such as:

• Customer default payment method will be used.
• Latest invoice payment method will be used.
• Customer default payment method will be set in the buyer account.
• Existing migrated subscription will be skipped.
• Trial anchor fallback may be needed.
• Trial has no payment method and must collect one before renewal.
• Latest invoice shows an already-consumed once coupon that will not be recreated.
• Repeating coupon window ends before the next renewal, so the subscription migrates without carrying the coupon.
• Source cancel-at-period-end state or a scheduled custom cancel_at timestamp will be mirrored.
• Source metadata exceeds Stripe's limit after RevBridge lineage keys are added, so copied metadata will be trimmed deterministically.

Operator rule

Treat blockers as execution-stopping conditions. Treat warnings as review-required conditions.