The Background jobs card at the bottom of the main part of your Dashboard has two tabs: Jobs (work VenueDB is doing for you) and Connections (whether everything you've plugged in is still working).
Jobs
Anything slow runs in the background so you can keep working. Today that's:
- Report exports — a CSV or PDF of a whole report (up to 50,000 rows), started from a report's Export menu.
- Scheduled report emails — each automatic send leaves an entry showing who it went to, or why it failed.
Each entry shows its status:
| Status | Meaning |
|---|---|
| Waiting | In line. It says how many are ahead of it. |
| Working… | Being prepared right now. |
| Ready | Finished. Exports show a Download button with the file size. |
| Failed | Something went wrong; the reason is on the entry. |
Finished files are kept for 7 days, then removed (the entry says how long is left). Click × to hide an entry you're done with. You also get a notification (the bell) when an export is ready or fails.
Only you can download your own files.
Fair-use limits
So that a few big exports can't slow VenueDB down for everyone, there are limits:
- Your venue runs 2 exports at a time; the rest wait their turn automatically.
- You can have 3 waiting or running at once.
- You can start 8 exports in any 10 minutes. Past that, VenueDB tells you roughly how long to wait before starting another.
- Your team can have 25 waiting in total.
Waiting is normal during a busy moment — the entry starts by itself when there's room.
Connections
The Connections tab answers "is everything still working?" It stays quiet when things are fine and speaks up when they aren't.
- A red count on the tab and a banner at the top of the card appear when something needs attention.
- The tab lists problems first, each with a plain-language reason and a link that takes you to the fix ("Reconnect", "Check the link", "View deliveries").
- When nothing is wrong it says All connections healthy. Show all lists every connection with when it last worked.
What's watched
| Connection | It's flagged when… |
|---|---|
| Google Calendar sync | The sign-in expired or was removed, or the sync hasn't run for 30 minutes. |
| Calendar feeds (webcal / .ics) | The link can't be read, or it hasn't updated for 3 hours. |
| Connected email | The inbox can't sign in. |
| Webhooks | Three deliveries in a row failed (a warning after one or two). It recovers after two successes in a row. |
| API keys | A key is being used and many of its requests fail — a warning at 5 failures and 25% of requests in a day, a problem at 10 and 50%. A revoked key, a missing scope and a bad request are all counted. |
| Payments (Stripe) | The connection has an error, or Stripe still needs information before it can take payments. |
| Scheduled report emails | The last send failed. |
Who sees what
- Everyone sees their own connections — their Google calendar and their email inbox.
- Managers and above also see the venue-wide ones: feeds, webhooks, API keys, payments and scheduled reports.
Alerts
When something starts failing, the right people get one notification in the bell with what's wrong. When it's working again, they get one more. You won't be notified every minute while it stays broken. Personal problems go to the person (and the managers); venue-wide problems go to the owners, admins and managers.
VenueDB checks every few minutes, and again whenever someone opens the dashboard.
API activity
Failed API requests are recorded against the key that made them, with the reason, for 14 days. That's what lets the Connections tab say, for example, "12 of 12 requests failed in the last day (403: API key is missing scope: read:leads)". See the API introduction.
Troubleshooting
| You see | Usually means | Do this |
|---|---|---|
| "the sign-in expired or was removed" | The Google or email account revoked access, or the password changed. | Click Reconnect and sign in again. |
| "the address couldn't be found" | A feed or webhook URL is wrong or no longer exists. | Open it and correct the link. |
| "the other side didn't answer in time" | The other service is slow or down. | Wait a few minutes; it recovers by itself. |
| "it doesn't have permission" | The key or account can't do what it's asking. | Check the key's scopes, or the account's permissions. |
| Export stays Waiting | Your venue is already running 2 exports. | Wait; it starts automatically. |