/signals). The page describes itself as “your
attention center across connected tools. Hive finds risks, explains why they matter, and proposes the
next safe step.”
Signals also keeps a list of your matters: the deals, invoices, applications and
disputes you have going on, read every hour from all the accounts you connected and linked across them.
When you ask Hive to keep an eye on something,
such as “tell me when the signed contract arrives”, it follows that as one of your matters too. The
page has two tabs: Attention (the feed) and Matters. One line under the tabs says what the open
tab holds: Attention is “Risks and follow-ups Hive spotted across your connected tools”, and
Matters is “Each piece of client work Hive is tracking, and what it is waiting on”.
Signals needs something connected to read. In a workspace with nothing connected the feed says
Connect a tool to get started, with a Connect a tool button that opens
Integrations. While Hive’s first read of a tool you have just connected is
still running, an empty feed says Hive is still reading your connected tools rather than that you are
all caught up.
Signals is an optional product, on by default for new workspaces. An Owner or Admin can hide it
under Settings → Products → Signals (Show Signals in this workspace). Existing workspaces
keep their setting. While it is off, Signals is missing only from the sidebar and the command
palette: Hive keeps watching your connected tools, and approvals stay reachable from
notifications and direct links. The setting is not a permission. Signals reads a member’s
accounts only once that member connects them: in a new workspace it reads nothing until then.
The Hive loop: connect your tools, catch what is slipping, approve with context, and let Hive earn autonomy.
What a signal contains
Every signal is built from the same parts, so you can read any of them the same way:
Hive never stores the label of the connected account (such as a mailbox address) on the signal itself; the
screen resolves which account a signal came from when you open it.
How Hive finds signals
Hive watches your tools in several complementary ways.The always-on loop
Hive runs an hourly loop across every live connector: it collects fresh data, runs detection, and reflects on what it has learned. Some tools also push changes to Hive as they happen through webhooks, and a tool you connect is synced straight away. Owners and Admins see when the next run is due at the top of the Signals page and on the Connectors tab of Integrations. There is no button to start a run.Real situations, not counts
Signals raises a signal only for a real situation: a person waiting on you, a conversation gone quiet, an invoice or deal slipping, or something on one of your matters that needs you. It does not raise count-style alerts such as “12 unread emails” or “files are shared publicly”, or alerts about a metric moving outside its usual range. For deals, Hive checks your own HubSpot deals every hour with its own rule and raises a Deal slipping card when one crosses a slipping line. When someone you correspond with on a deal, invoice or support matter is not in your CRM, it raises a Not in your CRM card with a ready Create contact action. Both wait for your approval.Until October 2026, Hive also wrote a monitoring plan for each connected tool and raised count and
anomaly alerts from it, listed on a Coverage tab. Those detectors are retired in every workspace: their
open signals were withdrawn as Coverage lost. The Coverage tab became a Watches tab, which is now
gone too: what you ask Hive to keep an eye on is followed as one of your
matters.
Matters and the Signals officer
Every hour Hive reads what changed in the accounts you connected — mail, files, calendars and systems of record such as Xero or HubSpot — into your matters, in every workspace. The Signals officer then decides what needs you on each matter: a reply owed, an invoice to chase, a payment you owe, a deadline to meet, a follow-up, a document waiting on you, a deal slipping, sources that disagree. Each becomes a signal linked to its matter. The officer also checks what you asked it to keep an eye on and raises a Waiting for met signal on the matter when it happens. Signals does not watch companies on Companies House; ask Hive about a company and it looks it up there. When your workspace has its firm on record, Signals is told only your firm’s name and its own domains, so “us” means your company and mail from your own colleagues is not mistaken for a customer’s. The reading of your accounts gets your website’s domain and the domains of your own work mailboxes; the officer gets your firm’s name and your website’s domain. See Your own company. Mail you only received as a copy — on Cc or Bcc, or through a group or forwarding address — never starts a matter or a signal. See Mail you were only copied on.Mail detectors
For Gmail and Outlook, Hive looks for conversations where someone is waiting on you (the last message came from them) and conversations that have gone quiet when you are waiting on someone else. A thread you were only copied on raises neither. A new mail signal needs a last message from the past 4 weeks, so the older mail Hive syncs when you connect a mailbox raises none; a signal already open stays open until the thread is answered. Mail signals carry no address, subject or excerpt in the signal itself; they point you back to the thread. You get one new Awaiting reply per person. When the same person is waiting on you in several threads, or in several of your mailboxes, Hive opens one card, for their longest wait, and opens none while a card for them is already open. Mail you wrote yourself is never a wait: a message from any mailbox you connected, or one Gmail or Outlook filed as sent from your mailbox (such as mail from an alias), counts as yours. Only your own mailboxes count, never a colleague’s. Automated senders such as order and shipping updates,support@ desks and mailings are skipped, and so is personal and consumer mail, such as a shop, an
airline, a utility, a clinic or a bank writing to you as a customer; see Email signals
for the full list.
Mail signals are raised for each member, only from that member’s own connected mailbox, and only that member
sees them. On Business, Signals watches every mailbox a seated member connects. On an
earlier plan, it watches one mailbox for each Max seat, the holder’s own: the connected mail account that
matches the email they sign in to Hive with, or else the first mailbox they connected. There, a member’s other mailboxes
are still read for Ask, search and their Business Brain, and signals already raised from them stay. Signals still
reads the member’s other connected tools, such as Xero, Stripe or HubSpot. A workspace still on a plan or trial it
started before the current prices keeps Signals on all of its Max holders’ mailboxes until it chooses or changes its
plan. Where Signals keeps your matters, the mail detectors defer to them: a thread gets one
signal, not one from each, and a thread your matters show is done is left quiet. Hive judges a thread only after a complete, recent sync of the mailbox — including Sent Items — has
finished after the thread’s newest message, so a reply you sent is never missed. Until then it raises nothing
and clears nothing. See Email signals for the details.
Connector-specific detectors
Hive also has detectors built for particular tools, such as invoice collection for Stripe and Xero, and stale assigned work for GitHub and Jira. These are rolled out per workspace and are not switched on everywhere by default. See the integrations catalog for what each tool supports.Severity and ranking
Severity is High, Medium or Low, and follows money and time:- Money at stake decides when there is any: an amount of 5,000 or more (in the source’s currency) is high, 500 or more is medium, less is low.
- Time decides a wait, such as a reply you owe: two to thirty days is medium. A one-day wait is low, and so is one that has gone cold for more than thirty days.
- Stage — what needs you comes first (see below).
- What is at stake — the money involved, how close the due date is (or how far past it), and how many days the signal has waited. A larger amount, an overdue date and a longer wait each rank a signal higher. These come from the signal’s own facts, not from the AI’s estimate. The due date is the due date of the matter the signal was raised on.
- Severity — high before medium before low.
- A priority score that combines severity, confidence and blast radius — how much the affected customer, deal or account is worth to the business, based on what the Business Brain knows.
Open a signal in Ask
Every signal’s details have Open in Ask. It opens Ask with the signal, and its matter when it has one, already written into the message box, and a From signal chip above it. Nothing is sent: add your question and send it yourself. Hive then already knows the signal, its matter, the email thread and app it came from, and the follow-up Signals prepared. Ask “draft a follow-up” and it prepares the reply card in that thread for you to approve, without searching your mail. The chat keeps this for your follow-up questions until you remove the chip. Only you get it: in a shared chat, a colleague’s questions don’t.Stages
Every signal sits in one stage, shown as a label on the row:Where the situation stands
Alongside its stage, a row can show where its situation stands:
The label names the furthest step Hive has evidence for. Paid and Resolved — they replied say what Hive
read in the source, not that Hive caused it. A declined action shows no label.
How Hive closes a signal on its own
When a condition clears by itself (the invoice gets paid), Hive closes the signal for you. It does so only on fresh evidence: a recent reading, taken within two of the source’s collection cycles (about two hours on the hourly loop), shows the condition is gone, or the source itself confirms it cleared. Events a tool pushes to Hive are judged by when Hive received them, so a delayed or retried event cannot clear a newer signal. When Hive cannot confirm a signal either way, it does not treat it as resolved. Instead the signal moves to Watching, a note above the list reads Can’t confirm — coverage incomplete, and the row is marked Unconfirmed. On a phone the note is one line, Coverage incomplete for N items; tap Why? for the full note. This happens when:- the latest reading is too old to prove anything;
- the provider refused the connection, for example because access expired or was revoked, or the account needs reconnecting;
- for mail, the mailbox has not completed a recent full sync (see Email signals);
- in a large workspace, the hourly pass did not reach the signal’s mailbox or account, and Hive has not seen the signal for more than two hours. A signal seen within the last two hours keeps its state (see When Hive judges a thread and Reading accounts on the hourly pass).
Noise control: gating, grouping and fatigue
A signal only reaches the feed after it passes an alert gate. It must be urgent, actionable, visible to you, not already covered by another signal, and not a type your team has shown to be noise. Signals whose action would have a high blast radius (B3 or B4) always go to a person.- De-duplication. If Hive detects the same situation again, it updates the existing signal instead of creating a new one. The row then reads, for example, “seen 2m ago · 47th time · first raised 9d ago”. See One situation, one signal.
- Grouping. When several related signals fire together (an alert storm), Hive shows one row with a count instead of many rows. Grouping stays within one person’s connected accounts: see Grouping is per person.
- Cooldown. Hive does not re-notify about the same thing repeatedly, but breaks the cooldown early if the severity gets worse.
- Alert fatigue. If a type of signal is dismissed as noise at least 80% of the time across at least five signals in the last 14 days, Hive stops notifying about that type. It is counted per account, not per workspace, and lifts on its own as those dismissals age out. See How dismissals reduce noise over time.
- Your own bar for medium signals. A high-severity signal that passes the gate always notifies you. A medium-severity one must also be confident enough to clear a bar that only your own feedback moves. See How Hive learns what to notify you about.
- Only places that exist. An action Hive proposes by itself posts to, or labels a note for, a chat
channel only when your connected chat app has that channel. With no chat app connected it proposes no
channel message, and no note for a
#channel. It never drafts, sends or replies to a no-reply address, such as a calendar service’snoreply@orcalendar-noreply@. - A gentle start for a new workspace. In a workspace’s first 14 days, Hive prepares at most 10 high-risk proposals for each member a day by itself. See Act on a signal.
One situation, one signal
Hive keeps one signal per situation: one per mail thread, invoice or record, in one member’s connected account.- Re-connecting keeps your signals. If you reconnect or re-authorise an account and the provider reports the same account, your open signals stay the same signals, with their history and triage, and no duplicate Inbox cards or approvals appear. For a tool that reports no account id, a re-authorised account starts new signals.
- A wait that comes back reopens its signal. An Awaiting reply or Went quiet signal belongs to the message that started the wait. If it resolved because a reply arrived, and the same wait comes back, Hive reopens the original signal and returns it to the top of the feed rather than raising a new one. New messages after your reply start a new wait, and a new signal.
- Dismissed and withdrawn signals stay closed. Hive never reopens them on its own; you can reopen a dismissed one for 7 days (see Reopen a closed signal). A situation that recurs later opens a fresh signal. After the safety ceiling withdraws a signal, Hive waits a day before it raises the same situation again.
- Separate stays separate. Two members connecting the same tool are always separate signals. Each thread is its own signal too, so answering one thread closes only that thread’s signal, though Hive opens a new Awaiting reply for a person only when none is open for them (see Mail detectors).
Grouping is per person
Grouping, alert-storm collapse and cross-tool signals only combine signals from one person’s connected accounts. A signal from your accounts is never covered, held back or silenced by a signal from a teammate’s, even when both are about the same company. The related findings count on a row includes only signals from the same person’s accounts, and each member gets their own cross-tool signal when their tools pile up on the same company.How Hive learns what to notify you about
Every high-severity signal that passes the alert gate notifies you. A medium-severity signal must also clear a confidence bar, and that bar is yours alone: it moves only with your own feedback on the notifications Hive sends you.- Useful. On a signal Hive notified you about, select Useful: in the row’s Details, next to Dismiss, or, when Hive has prepared an action for it, in the review panel the row opens. The button stays highlighted while your mark stands, and a row with Details also shows Marked useful. Each notification you mark useful lowers your bar a little, so Hive notifies you about more like it. To take the mark back, select Useful again. It is offered while the signal is open: once you decide its action, or it closes, its notification is done.
- Dismissing a notification raises your bar a little, so fewer reach you. An AI client connected through the Hive MCP server can mark a notification useful or dismiss it for you. Dismiss on a signal’s row closes the signal itself and teaches Hive through the reason you give instead: see Dismiss: say why.
- A teammate’s feedback never changes what Hive notifies you about, and yours never changes theirs. The one shared case is sample data, which every workspace Owner sees: there, the last Owner to mark a notification is the one whose feedback it is.
- Hive’s own housekeeping is not feedback. A notification Hive closes because its approval was decided, because a workflow approval was settled, or because its signal was withdrawn does not count, and neither does marking a notification read.
- Feedback on a notification that is not about one of your signals, such as a workspace notice, does not count.
- Feedback from before 4 October 2026 does not count, because Hive did not record whose it was. Every member’s bar started again from the default then.
A quiet feed does not automatically mean all is well. It can also mean a source is delayed or a permission is
missing. Check each account’s read status on the Matters tab and on the Integrations page before
treating silence as reassurance.
Evidence and provenance
Each reading names its source connector and field, and can show what it was compared against. Comparisons are labelled in plain words — “past your threshold”, “against your usual”, “corroborated”, “correlated” or “cited” — so you can tell a measured breach from a supporting observation. Source links always point to the original record over a secure link and never contain credentials.Illustrative example with synthetic data: a signal shows its source, freshness, evidence and known limitations.
Who can see a signal
Every signal belongs to one member: the person who holds the account it was read from, or whose matter or watch raised it. No one else sees it — not a teammate, and not a workspace Owner or Admin:- The holder sees and works it. Only a member who holds every account a signal was read from, with the access they granted still current, sees it in the feed, its counts and its details, and can act on, snooze, dismiss or approve it. The same applies to the notifications and Inbox cards it raises, the approvals it leads to, the receipts it leaves in the activity feed and audit log, and what Ask Hive, the daily brief and the health and impact reports can draw on.
- Company systems are no exception. A signal read from a business tool a member connected — for example Stripe, Xero or HubSpot — is theirs alone, exactly like one read from their mailbox (Gmail, Outlook) or synced files (Google Drive, OneDrive, SharePoint, Dropbox and the Google and Microsoft document tools). Owners and Admins have no read-only view of other members’ signals.
- The same holds everywhere. Ask Hive, the daily brief, the health and impact reports and an AI client connected through the Hive MCP server use only the signals you hold yourself. An Ask answer built from your signals is part of its chat, though: sharing a chat shares everything in it, so share only with people who should see that. See Feedback, sharing and history.
Until October 2026, Owners and Admins could read other members’ signals from business tools, read-only, and
switch the feed between Everyone and Mine. Both have been removed: every signal is now its holder’s
alone.
When Hive loses access to a source
When the access a signal was read under goes away, Hive withdraws the signal rather than leaving it open or marking it resolved. A withdrawn signal is closed and moves to Done for 7 days, and its pending approvals are removed, so nothing can act through access that is gone. It cannot be reopened. The notification Hive raised about it is withdrawn too, even when Hive had notified you before the signal was withdrawn, unless you had already marked it useful or dismissed it. The signal reads Done and says why it closed, as Closed by Hive · and one of the reasons below, followed by “No completed action is confirmed.”:
Hive never withdraws a signal because it could not prepare a response to it. The signal stays in your feed with
its notification, as being prepared. Hive retries a failed preparation automatically, and if it still cannot, Hive’s
team is alerted and re-runs it. There is nothing for you to retry. See
Act on a signal.
A cross-tool signal is withdrawn too when it drew on a disconnected account, or when it no longer holds up
without a signal Hive withdrew. Nobody judged a withdrawn signal, so it does not count toward alert fatigue for
its type, either as surfaced or as dismissed, and its notification does not count as feedback on what is worth
notifying you about (see How Hive learns what to notify you about).
Some signals are left as they are:
- A signal whose action is already running is not withdrawn.
- A tool with no account left does not close a signal someone has already taken up. A retired count-style detector’s signals were withdrawn whoever had taken them up, unless their action was already running.
- Nothing that was already approved or already ran is undone.
Fair use and credits
On Business, Signals comes with every seat, Basic, Pro and Max alike, and during the trial too: Hive analyses what arrives in each seated member’s connected accounts. There is no fair-use allowance and no separate Signals cap: finding what needs attention and preparing replies and actions use the AI credits of the member whose accounts Signals reads, at what the work costs Hive. A signal raised from several members’ accounts is paid for by whoever’s account raised it first, and acting on a signal yourself uses your own credits. When a member has no credits left to pay for it, the work on their accounts waits and Hive picks it up again on a later pass. See Who pays. The rest of this section describes Signals on an earlier plan (Starter, Team or the earlier Business plan). Signals is part of the Max seat: Hive analyses what arrives in the connected accounts of each member who holds one, with one watched mailbox per Max seat. Members on a Pro or Approver seat see the approvals routed to them, but Hive does not read their accounts for Signals, and they cannot choose Act on this or set a watch: the Signals page tells them why. Hive still syncs a Pro member’s connected accounts so Ask and search can use them, but raises no signals from them: none from their email, files or app events, and no meeting recaps from their notes. A member on an Approver seat connects no accounts. A member without a seat, or whose seat is suspended over the plan’s limit, can do nothing in the workspace, and Hive reads none of their accounts until they have a seat again. This is the same on every earlier plan, including a trial that began before Business went on sale. When a member’s Max seat changes to a Pro or Approver seat, or they lose their seat, the Signals proposals and prepared drafts waiting for them are withdrawn. Within the seat’s fair use, Signals never touches your workspace’s credit pool, so other people’s usage cannot stall it. Fair use per Max seat each month:
Fair use belongs to the seat, not to the person holding it. If an Owner or Admin moves a
Max seat to someone else during the month, or changes who holds the workspace’s
Max seats, the new holder carries on from what the seat has already used: its items,
prepared actions, priority lane, 60 automated emails a day and included first reads do not start
afresh. Together the workspace’s Max members use at most one seat’s fair use for each
Max seat it pays for (during the trial, for each one held this month), and no one member
uses more than one seat’s.
If a member on a Max seat leaves, or moves to another seat type, and nobody takes their seat, what
they used stays with that seat: the other Max seats keep their own fair use. Included first
reads count over any 90 days, so a seat you stop paying for at the end of a billing period keeps the
first reads it used, without taking those of the seats you still have.
Starter’s fair use is sized for a light mailbox, so a busier Max member goes above it sooner.
Above fair use, each new item analysed uses about 1 credit from the pool, each prepared action
about 11 and each client reply about 12, up to the member’s limit for Signals above fair use: 2,000
credits (£20) a month by default. Owners and Admins can lower it, to 0 if they like, under
Settings → Usage → Spend controls.
A Not in your CRM card is not a prepared action: Hive’s own
rule prepares its Create contact, with no AI, so it uses no prepared action and no credits.
Chases are not prepared actions. Each chase Hive drafts counts against the workspace’s
templated chases: 300 a month for each Max seat it pays for, shared across the
workspace, then 3 credits each from the pool. A chase the pool cannot pay waits for you as
needs reply. On an account set
to Act, Hive sends at most 60 emails by itself per Max seat a day; past that, the
next email waits for you as an approval card. Only an email that goes by itself counts, once: one
that waits with the rest of its plan for your approval is not counted, and nor is a retry. When Hive
detects the same signal again later that day (an invoice still overdue), the email it sends then is
a new one and counts too.
A signal is counted once: if Hive retries a read or a preparation, it is not counted against your
fair use, or charged, a second time. Nor is it when something on its matter changes again (a new
revision of an invoice Hive just chased, say) while the signal is being prepared, waits for you or
has been handled: Hive updates the signal and leaves its card as it is, rather than preparing it
again.
Beyond that limit, or when the pool is empty, Hive keeps a priority lane running at its own
cost: items linked to your open matters or from your priority senders are still analysed, up to 500
a month, on an Efficient model. Other items above fair use are still read, and mail that is waiting
on your reply arrives as needs reply with no draft prepared: it shows as a Needs reply signal
with the thread’s own subject, read from your account but not analysed by a model. Only mail someone
is waiting on you to answer becomes a Needs reply signal: meetings, document changes, records, mail
you were only copied on and threads where you wrote last do not. A thread shows once: mail Hive
already shows as Awaiting reply is not repeated as Needs reply, and a thread held as Needs reply
is not shown again as Awaiting reply. When Hive reads your reply while you are still above fair use,
it closes the Needs reply signal; you can also dismiss it yourself. Choosing Act on this on one counts as a prepared action: within fair use it
is included, and above it it uses credits from the pool, whatever the limit for Signals above fair
use. If the pool cannot pay, or it would take you past your own monthly credit limit, Hive does not
start it: the Signals page says why straight away. An
Owner or Admin on a paid plan can buy a credit top-up there in one click and then choose Act on
this again; other members are asked to have an Owner or Admin add credits, or raise their limit.
A preparation that was already paid for and then could not start, whether Hive prepared it
automatically or a member chose Act on this, is not charged again or counted as another prepared
action: preparing it again is never refused for credits, even when that payment emptied the pool, the
month has since rolled over, or Hive has seen the same situation again in the meantime. If Hive
prepares the signal again by itself, that uses the same payment too.
A preparation that fails on Hive’s side (the AI provider is down, say) delivers nothing, so it costs
nothing: the signal stays in your feed as being prepared and its payment comes back. The prepared action returns to the
seat’s month, or the credits come back to the pool, valid for 12 months (during the trial, as trial
credits until the trial ends), and no longer count toward the member’s limit for Signals above fair
use. This holds whether Hive prepared the signal by itself or a member chose Act on this. Hive retries
it automatically, and if it still cannot, Hive’s team re-runs it.
The usage page and the month-end forecast under Settings → Usage show a Signals above
fair use line, and each member sees their own fair use under Settings → My usage.
Flood limits. Hive analyses at most 100 new items per member an hour and 2,000 a day. Items
beyond that wait for a later read; nothing is dropped. Owners and Admins are alerted when a
member’s day reaches 5 times their usual daily level. The first read of a newly connected account
is included in the seat and does not count toward these limits or fair use, for up to the seat’s
account allowance in any 90 days (3 accounts on Starter, 6 on Team and above, 2 during the 7-day trial).
First reads beyond the allowance. Once a seat’s included first reads in the last 90 days are
used, the first read of the next account you connect uses credits from the pool at measured cost
(during the trial, from the trial credits): about 100 credits for a light account, 180 for a
typical one and 450 for a heavy one, at most about 1,050. It does not count toward the flood limits
or fair use either. Connectors says so before you connect the account. Like your own work, it
counts toward your monthly credit limit and the workspace’s maximum monthly spend. If the pool or a
limit cannot pay, the read waits until credits are back: you and the workspace’s Owners and Admins
get one Needs you card for the account, naming its app and what lets it go ahead (choosing a
plan during the trial, a top-up, a higher limit or paying an overdue invoice). The card clears once
the account is read, including when a plan you choose or room freed in the last 90 days makes it an
included first read, and when you disconnect the account. It also clears when the account’s member
leaves the workspace, and at Signals’ next hourly pass once they no longer hold a Max
seat: their accounts are not read then. When several new accounts come in together and not all of them fit the
included first reads, none of them uses one: that read is charged, and each account keeps its
included first read for later.
Accounts connected before a Max seat. Connectors shows the cost of a further first
read only to a member on a Max seat, so an account connected before its member held the seat (a
Pro member later given a Max seat, say, or a member whose suspended seat came back) is
never charged for its first read. It uses one of the seat’s included first reads if one is free.
If none is, it waits, unread and uncharged, and the member and the Owners and Admins get one
Needs you card for it saying so. It is read in the seat once an included first read is free
again; to have it read straight away at measured cost, disconnect it and connect it again, and
Connectors shows the cost first. Reconnect on the account does not end the wait, since it
keeps the same connection. Disconnecting removes what the account added to the Brain until its
new first read adds it back. Only that account waits: your other accounts are read as usual,
including mail about the same clients, invoices or deals, and the waiting account’s items join
those matters once it is read.
Accounts connected before your workspace’s plan began. If your workspace was using Hive before
its first plan or trial started, the accounts connected before then, or within six hours of the
new plans arriving while that update was still rolling out, are read in the seat when Signals
first reads them: they use none of the seat’s included first reads, never wait for one, and are
never charged, however many there are.
Safety limit. Each workspace also has a daily safety limit on the work Hive does to find and
prepare signals, which grows with its Max seats and which normal use does not reach. It
only stops a fault from running up work without end, and if Hive cannot check it, the work waits.
If a workspace does reach it, Hive withdraws a new signal it can no longer prepare before it
notifies anyone, so it leaves no notification behind. A signal that was already being handled stays open and keeps its
notification. The hourly read of your matters waits instead: nothing is chased and nothing you are
waiting for is marked as met until the limit resets at midnight UTC, so nothing is lost.
While a payment is overdue, Signals keeps running for every Max seat. While the workspace
is read-only (its trial ended without a plan, its plan was cancelled, or a payment has been overdue
for 14 days), Signals pauses; your signals and data are kept.
Related
Triage signals
Act on, snooze or dismiss a signal, and what each choice changes.
Keep an eye on something
Ask Hive to tell you when something happens, and it follows it as a matter.
Review and approve
Decide on the actions Hive proposes.
Trustworthy signals
The principles behind every signal Hive raises.