The provider alert bells

Setup catches an unready account before you start. These bells catch a provider that stops mid-flight, once you're up and running.

There are six: two for Apify, one each for BrightData and Gemini, and two for YouTube. YouTube's Data API is free, so its two aren't about money: one says the key was refused, one says Google's daily allowance ran out.

Each rings at most once a day while the cause holds. Each one reaches the account managers of the affected clients, plus everyone who can manage your provider keys — and those key-holders get an email too.

Apify

Apify has two bells.

Your Apify plan needs attention. Your Apify account has no active paid plan — collection and analysis can't run fully. Everything resumes once it's on a paid plan.

Fix: put the Apify account back on a paid plan. The four providers shows what each one powers.

Your Apify usage limit was reached. Your Apify account hit its monthly usage limit, so everything that runs on Apify is paused until the next billing period or until you raise the limit in Apify under Billing, Limits. The limit is also your spending cap - raise it only as far as you're comfortable paying.

Fix: raise the limit in Apify, or wait for the next billing period.

BrightData

Your BrightData account needs attention. Your BrightData account is suspended or out of funds — scraping is stopped. It resumes once the account is funded and active again.

This is the one to act on quickly. A dead BrightData account stops collection across the whole agency, and the posts missed while it's stopped are gone for good.

Fix: add funds or clear the suspension in BrightData.

Gemini

Your Gemini account is out of credits. Your Gemini key has no usable credits — AI analysis is stopped, though new posts still arrive. It resumes once your Google AI Studio account has credits.

Fix: buy credits in Google AI Studio. New posts keep arriving the whole time — they simply wait to be analyzed. See out of Gemini credits.

Your YouTube key was refused

Your YouTube API key was refused — new YouTube posts aren't being collected. Whoever manages your provider keys can re-test or replace it in Settings to resume.

This is the only YouTube bell that means something is broken. Huntit re-tests the stored key itself when it fires, so the Credentials panel stops claiming the key is fine.

If you're the one who can change keys, your copy of the bell says so and tells you to act.

Your YouTube key hit its daily limit

Your YouTube key used up Google's free daily allowance. The busiest channels you track have paused until it resets tomorrow — everything else keeps collecting. Your key is fine; nothing needs replacing.

Nothing is wrong and nothing needs pasting. Clicking it opens a reading window rather than Settings, because there's nothing to fix on that row.

If it fires most days, a few very active profiles are using up the allowance on their own. Pause the ones you no longer need, which frees the allowance at the next check. Or send us a ticket saying which profiles matter most, and we'll go through your tracking with you.

How they behave

• Once a day. A stopped account won't flood your bell.
• Where a click lands. Most bells open Settings → Credentials on that provider's row, where the state and the Re-test are. The allowance bell opens its own reading window instead.
• They clear themselves. Fix the cause and the condition stops firing. Nothing to follow up.

For what the states on those rows mean, see reading your key states.