Maintenance·2026.09.13·2026-09-14

Gift recipient cutover and pause recovery

The durable sender candidate preserves a recipient-only pause and recovery path. Gift value, redemption and ordinary purchase receipts remain available.

# Temporary gift recipient delivery hold

Historical bridge notice: the successor source enables the durable sender only
after the reviewed SQL93 cutover. This notice describes the bridge/rollback mode,
not a claim that maintenance is currently active or has already ended in production.
The successor's same-schema pause also stops queued recipient work before claim
and at the final provider hook; verified callbacks and giver receipts continue.

This separately reviewed, migration-free bridge temporarily holds gift-recipient email and SMS delivery, including resends, scheduled deliveries and forwarding. It does not disable other notifications, purchase receipts, existing gift value or redemption. Forwarding cannot change recipient information during the hold.

Payment confirmation remains recorded before delivery is refused. A held recipient notification is not a failed payment, a sent message or activation. Keep the original purchase/receipt and do not purchase again to retry delivery. Staff explicit no-notification issuance remains available under its existing paid-card guards.

The source candidate does not itself authorize or perform maintenance. Deployment requires owner authorization and the normal staging/production release gates. Old deployments and in-flight/background workers must be excluded and drained with measured runtime evidence before the separately reviewed durable delivery migration can proceed. A five-minute cron lock or quiet notification ledger alone does not prove this.

Next update

BB Sites AI provider failures are now explicit

Website chat now preserves the provider's real failure and clearly identifies when platform provider credits must be restored.

# Temporary gift recipient delivery hold Historical bridge notice: the successor source enables the durable sender only after the reviewed SQL93 cutover. This notice describes the bridge/rollback mode, not a claim that maintenance is currently active or has already ended in production. The successor's same-schema pause also stops queued recipient work before claim and at the final provider hook; verified callbacks and giver receipts continue. This separately reviewed, migration-free bridge temporarily holds gift-recipient email and SMS delivery, including resends, scheduled deliveries and forwarding. It does not disable other notifications, purchase receipts, existing gift value or redemption. Forwarding cannot change recipient information during the hold. Payment confirmation remains recorded before delivery is refused. A held recipient notification is not a failed payment, a sent message or activation. Keep the original purchase/receipt and do not purchase again to retry delivery. Staff explicit no-notification issuance remains available under its existing paid-card guards. The source candidate does not itself authorize or perform maintenance. Deployment requires owner authorization and the normal staging/production release gates. Old deployments and in-flight/background workers must be excluded and drained with measured runtime evidence before the separately reviewed durable delivery migration can proceed. A five-minute cron lock or quiet notification ledger alone does not prove this.

All updates