Troubleshooting common issues

OAuth-based connections (Google, Meta, Twitter, Instagram, Facebook Business) carry access tokens that expire or get revoked on the provider's side, not BrandOps's.

• Settings → Integrations flags any connection where this has happened with a visible "expired" warning on that platform's card, so you don't have to guess why a sync stopped.
• Google's card covers YouTube Analytics, Google Analytics 4, Search Console, and Google Ads all through one OAuth connection. If it needs reconnecting, all four stop syncing together.
• Reconnecting is just running through that provider's OAuth consent screen again; it doesn't reset or lose any historical data already synced.
• If a scheduled sync (like the ad-spend cron job) hits a needs-reconnect account, it skips that account rather than failing the whole run for every other connected account.

BrandOps checks every outbound email against a per-organization suppression list before it sends. This is a deliberate deliverability safeguard, not a bug.

• An address lands in EmailSuppression after it bounces or files a spam complaint, and every future send checks that list first.
• This applies at send time, live, not just once. A brand-new lead record you re-import or manually re-add for an address that was suppressed weeks ago has no memory of that history, but the live check still catches it and blocks the send.
• This exists to protect deliverability for your whole list. One bad address kept getting hit doesn't just hurt that recipient; it damages your sender reputation for everyone else on outreach and campaign sends.
• If a contact insists they never opted out but isn't receiving mail, check whether their address is suppressed before assuming a template or sequence itself is broken.

BrandOps gives every organization a 14-day trial. Once trialEndsAt passes with no plan chosen, a full-screen plan picker takes over instead of a hard redirect.

• The overlay sits on top of whatever page was already rendering. It doesn't send you anywhere, so picking a plan just makes it disappear and leaves you exactly where you were.
• It polls for payment completion automatically (roughly every 15 seconds) while locked, since a Razorpay payment can complete in another tab or take a few seconds for the webhook to land. You don't need to refresh manually.
• A handful of pages, including Daily Ops, Brand Kit, and Notifications, are explicitly allowed to stay reachable even while locked, so a lapsed trial doesn't cut off everything at once.
• Only the account owner can complete a plan purchase for the organization. If you're not the owner and see this screen, you may need to ask them to upgrade.

A newly connected integration or a recently changed setting doesn't always reflect everywhere instantly. A few things are worth checking before assuming something's broken.

• A fresh OAuth connection needs its first sync cycle to run before analytics, ad spend, or content data populates. This can take a few minutes depending on the provider.
• If a connection needed reconnecting and you just fixed it, scheduled syncs pick it back up on their normal cadence rather than immediately. Check Settings → Integrations to confirm the connection itself is now healthy.
• Business type changes apply instantly to your sidebar, but they don't retroactively create data for modules you've just gained access to (e.g. switching to Consulting doesn't backfill Clients). You start those modules from zero.
• If something still looks wrong after checking the above, it's faster for support to help if you can note which page, which integration, and roughly when it stopped looking right.