Notifications, logs, and monitoring

There are three independent ways to check. 1) In your dashboard open the "Logs" section (top menu) — green lines appear there: "POST PUBLISHED: " (in Hebrew "פוסט פורסם") with an FB or MP tag and a timestamp. 2) Next to such a line you'll see a 120×80 thumbnail preview — a real screenshot of the feed after publishing (click it to open full screen). 3) Your personal Telegram bot sends a checkmark and a photo after every post, and once an hour a card: "📊 Stats · ✅ Posts: X of N · Rate: Z%". If fresh screenshots keep appearing and X grows hour by hour, the bot is working.

It's the summary of a single hourly posting cycle. N is how many posts were planned for that hour (based on your "posts per hour" setting), and X is how many were actually published in the cycle. For example, "✅ Posts: 7 of 8" means 7 of the 8 planned went out. In the technical log the same info looks like "[HOURLY STATS] SRV-N | HH:MM | OK:7/8 Rate:88%", where Rate is the success rate for that specific hour (7 of 8 = 88%), not over all time.

To the Telegram you linked to your dashboard (to your Telegram ID). During setup your ID is written at the same time into the bots on the server (FB and MP) and into your personal listings bot — so they all message you directly. On top of that, the panel duplicates critical alerts through the shared @BuzzPostLinkBot. The exact name of the bot that sends notifications for each server is shown in the dashboard → "Notifications" section → the line "📨 Notifications come to @username".

The main ones: a screenshot of every published listing (for groups — "✅ POST PUBLISHED" + photo; for Marketplace — "✅ MP post published / 💰price₪ · 🛏rooms · 📍city" + photo); Facebook limited activity (rate-limit); the Facebook session dropped (you need to log in again); the Telegram session for collecting listings died; the server is unresponsive / back online; the bot stopped (paused or payment); for groups — a server-start message and an hourly stats card; in the dashboard feed — "Payment received ✅" and "Referral bonus 🎁". Emails are only sent for a Facebook rate-limit, an expired Facebook session, and a password reset.

Yes, that's by design: after every successful post the bot sends a photo of your group feed or your Marketplace card so you can see the listing really went out. One important detail: these screenshots come straight from the bot, so "Quiet hours" and "Do not disturb" do NOT mute them — they'll arrive even at night. There's no separate "don't send screenshots of successful posts" button in the dashboard. If the stream bothers you, you can turn off the "💬 Telegram" toggle for a specific server in the "Notifications" section, but then the panel alerts for that server will go silent too.

Dashboard → "Notifications" section → the "🌙 Quiet hours (Asia/Jerusalem)" block. Set a window, for example 22 to 7 (those are the defaults), and click "Save". During that time, in Jerusalem time, panel notifications won't come through. The "Reset" button removes the window. Note: direct messages from the bots (post screenshots, the pinned Facebook rate-limit message) are not silenced by quiet hours — for complete silence use "Do not disturb".

Dashboard → "Notifications" → the "🔕 Do not disturb" block → pick a preset: "1 h", "4 h", "Until morning", or "24 h". A banner "Notifications muted until …" appears. To bring the sound back sooner, click "Unmute". This mutes all panel notifications (both Telegram and email) across all servers at once. It stays in effect until the chosen time runs out or you unmute it manually.

Yes. In the dashboard → "Notifications" → the "Per server" section, each server has two independent toggles: "💬 Telegram on/off" and "📧 Email on/off". They work separately — you can keep Telegram and turn off email, or vice versa. This is configured separately for each server.

That's normal — not every colored line means something broke. The bot handles many of them itself: it skipped an unavailable group, retried, restarted Chrome due to a resource shortage (the slot is simply skipped and comes back later). Serious things — a Facebook rate-limit and "session dropped" — are deliberately NOT marked as a bot error; they get their own banner and notification. The one key indicator: if "POST PUBLISHED" lines and the hourly "Posts X of N" keep showing up, the system is working.

Not necessarily. 0 of 8 means nothing was published that hour, and the reason is usually noted in parentheses: "(content not received)", "(network unavailable)", "(Chrome failed to start)" — these are one-off situations; the slot is skipped and retried the next hour. But if it also says "Facebook session dropped" next to it, you need to log in via VNC and sign back into Facebook (you'll also get a notification and a banner in the dashboard about this). And zero posts often simply means you've run out of new listings to publish — that's normal too.

Nothing special. This is a limit from Facebook itself, not a bot error. The bot pauses and resumes on its own. For groups the pause escalates: 3 hours → 6 hours → 24 hours (depending on how many blocks in a row), and for Marketplace it's a fixed 30 minutes. The message/email states exactly how long the pause is. If the blocks keep recurring, it's worth checking the quality of your text and photos, or taking a couple of days off.

Yes. If the server (VDS) is unresponsive for more than about 10 minutes, the panel sends "🔴 Server not responding, down for N min" with a link to the server page, and when it comes back — "✅ Server back online, downtime N min". These alerts respect "Quiet hours" and "Do not disturb". If you haven't turned them off, you'll learn about an outage and the recovery without even opening the dashboard.

This is on purpose, to avoid spamming you with trivia. One-off, temporary failures are written only to the log file, and the bot escalates to Telegram only when many errors pile up in a row or something truly critical happens (session dropped, rate-limit, zero posts for the hour). Successful posts, on the other hand, are always shown. So silence about errors is the norm — watch for fresh screenshots and the hourly stats.

In three places. 1) Right in the "Logs" section: each post line has a 120×80 thumbnail; clicking it opens the image full screen. 2) In "Full post history per server" — at the bottom of the "Logs" section click the button for the server you want (it opens /v2/server//history): there you'll find post cards with a screenshot, timestamp, and group link, with counters at the top — "Total posts", "Last post", and "Unique groups". 3) The bot also sends every screenshot straight to your personal Telegram bot as a photo.

The feed refreshes automatically about every 60 seconds, plus there's a "Refresh" / "רענון" button for manual updates. The data comes from a shared server poll that is itself cached for about a minute, so the real delay before a fresh line appears can be up to 1–2 minutes. It's close to real time, but not second by second. To have the feed auto-scroll to new lines, switch on the "Live tail" toggle (with the pulsing green dot).

FB is the bot that posts to Facebook groups, MP is the Marketplace bot. SRV-1, SRV-2 are your server numbers (the feed is shared across all of them, and the tag shows which server a line belongs to). The toolbar has a bot filter "All/FB/MP", a time filter "1h/6h/24h/All", and search. The line color indicates the event: green — success/published, red — error, yellow — warning.

There's no separate "Errors" button — there's a bot filter (All/FB/MP), a time filter, and search. Errors stand out by their red highlight; to find them quickly, type something like "FAIL" or "failed" in the search. You also can't download the raw log file from the dashboard: it shows a filtered feed of important events (the last ~40 lines per server) and post history with screenshots. The full technical log lives on the server itself, and support can review it if needed.

A screenshot is taken only after a successful post and added to the log with a separate marker. If a line has no image, it's usually a service line (bot start, hourly stats, a warning), and those aren't supposed to have a screenshot. "Full post history" deliberately shows only posts with a screenshot so there are no empty cards — which is why entries without an image don't appear there. Also, the server keeps about the last 50 screenshots, and for very old posts the preview may become "unavailable" — that doesn't mean the post didn't happen.

The bot pins only critical events so they stay at the top of the chat: a dropped Facebook or Telegram session, a rate-limit, "no new listings 3 times in a row". Ordinary post confirmations and hourly stats are not pinned. The pin is removed once the event is over — for example, when the rate-limit cooldown ends. By the way, the hourly stats card doesn't create new messages; it updates over the previous one so it won't spam you.

Emails are sent from [email protected]. Only three types go to email: a Facebook rate-limit, an expired Facebook session, and a password reset — everything else goes to Telegram. If emails aren't arriving, check your "Spam" folder and make sure the "📧 Email" toggle is on for that server in the "Notifications" section. The footer of every email has support contacts: Telegram @BuzzPostil and WhatsApp +972-58-638-4995.

No. "Quiet hours" and "Do not disturb" are global — for the whole account at once. Only the channel toggles are configured per server: "💬 Telegram" and "📧 Email" (to turn a specific server's notifications on or off). You also can't set quiet hours in an arbitrary time zone — the window is always calculated in Jerusalem time (Asia/Jerusalem).

No, it just means you don't have a single running server with bots yet, so there are no events. The page has a "+ Order your first server" button. Once the server is deployed and the bot starts working, the lines appear automatically — the first batch within about a minute of launch.