> ## Documentation Index
> Fetch the complete documentation index at: https://help.superhawk.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What Runs Automatically

> The work Superhawk does on a schedule, and what to expect when.

Superhawk is a background system with a user interface, not a tool you operate. This page covers what runs, roughly when, and how to tell whether something has caught up yet.

## Source syncing

Each integration syncs on its own cadence. The connection card on **Integrations** shows the last successful sync for each one, which is the first place to look when something seems stale.

Syncing is incremental after the first pass. The initial sync on a new connection takes considerably longer than the ones after it, and on a large CRM it can run for hours.

## Call analysis

When a new transcript arrives from your call recorder, Superhawk analyses it: stakeholders, what was said and by whom, commitments made, friction raised, adoption blockers, outcomes named, and sentiment.

A call analysed today feeds every downstream judgement -- health, signals, briefs, memory -- from that point on.

## Metric computation

Metrics run on a schedule against every account. See [Metrics](/customer-success/metrics).

## Health judgements

Account health is recomputed on a schedule, and also when significant new evidence arrives. Every verdict carries the time it was computed, so you can always tell whether it has seen this morning's call.

## Signal detection

Detection runs continuously across every source. A signal that re-detects over the same ground supersedes the previous one rather than duplicating it -- see [Signal Lifecycle](/signals/lifecycle).

## Task drafting

When a signal warrants action, or a commitment made on a call comes due, Superhawk drafts the task with its evidence attached and puts it in your [Inbox](/inbox/overview).

## Brief generation

Briefs are generated ahead of meetings on your connected calendar, and regenerate if the meeting changes or significant evidence arrives before it. You are notified when one is ready.

## "It has not updated yet"

Work through it in this order:

1. **Check the last sync time** on the relevant integration. If the source has not synced, nothing downstream will have moved.
2. **Check the computed-at time** on the health verdict. If it predates the evidence you are expecting it to reflect, the next run will pick it up.
3. **Check the source actually contains it.** A call that was not recorded, or a ticket in a queue outside the connected scope, cannot reach Superhawk.
4. **Give a first sync time.** Initial syncs on a large account base are slow, and everything downstream waits on them.

<Note>
  There is deliberately no manual "recompute everything" button. Judgements are scheduled so that what you see is consistent across the portfolio rather than depending on who last pressed a button on which account.
</Note>

## Related

* [How Superhawk Works](/how-it-works/overview)
* [Accuracy & Limits](/how-it-works/accuracy-and-limits)