# Troubleshooting

> What to do when notifications are missing, pushes do not arrive, or Hush shows an error.

Source: https://hush-gh.com/docs/troubleshooting

## An org or a repository is missing

The org has probably not approved Hush. GitHub then hides the org completely. Check the list in **Settings → General → GitHub access**. If the org is not there, choose **Request approval**, and [use a custom token](https://hush-gh.com/docs/github-access#custom-token) until an owner approves Hush.

If the org uses SAML single sign-on and the inbox says “GitHub hides notifications from N orgs”, sign in again and authorize Hush for those orgs.

## “Hush cannot read your notifications”

The token no longer works: you revoked Hush on GitHub, the token expired, or a custom token was deleted. Choose **Sign in again**. With a custom token, replace it in **Settings → General → GitHub access**.

## A thread is in the wrong list

- Look at the row: its summary says why Hush put it there, and “rule: …” names the rule that sorted it.
- Check your [rules](https://hush-gh.com/docs/rules): the first rule that matches wins, so a wide rule at the top catches more than you expect.
- Bots' activity is FYI by default ([`botsAreFyi`](https://hush-gh.com/docs/settings#botsarefyi)), and so are team review requests ([`teamReviewsAreAction`](https://hush-gh.com/docs/settings#teamreviewsareaction)).
- Press `R` to check GitHub again now.

## A thread did not leave Needs you

Hush sees your own review, reply, or push within 15 minutes, because GitHub sends no notification for them. Press `R` to check at once, or choose **Done**.

## Pushes do not arrive

1. In **Settings → Notifications**, check that this device says “Receives push notifications.”, and choose **Send test**.
2. Check that your system allows notifications from the browser, and that focus modes or Do Not Disturb are off.
3. Check [quiet hours](https://hush-gh.com/docs/notifications#quiet-hours), and that the thread is one that gets pushed: by default only Needs you. A rule with `"push": false` stops pushes too.
4. On iPhone and iPad, push works only when Hush is on the Home Screen.
5. Turn push off and on again for the device.

Pushes can come a few minutes after the event: Hush checks GitHub every 5 minutes while push is on.

## The Pull requests or Issues tab is empty or incomplete

- The sections are GitHub searches. Choose the link button next to a section in **Settings → PRs & issues** to try its search on GitHub.
- Check the **Scope**: it is added to every search.
- `@team` sections need your teams. If **Teams** says “GitHub reports no teams for you”, the token needs `read:org`, and SAML orgs must authorize it. Choose **Look up teams again** after you join a team.
- Hidden items: press `H` to show them.
- Drafts that others opened and PRs that bots opened are hidden by default: see [`dash.hideOthersDrafts`](https://hush-gh.com/docs/settings#dash-hideothersdrafts) and [`dash.hideBots`](https://hush-gh.com/docs/settings#dash-hidebots).

## settings.json does not save

Hush shows the first error under the box, and saves nothing until the file is valid. The error names the setting, for example `"quietHours.timeZone is not a known time zone."`. The type and the allowed values of each setting are in [settings.json](https://hush-gh.com/docs/settings#every-setting).

## An action in the peek is not there

Hush shows only the actions that you can do now. Look in **More**: a blocked action is there with the reason, such as “It has merge conflicts.” or “You cannot merge in this repository.” See [Actions on GitHub](https://hush-gh.com/docs/peek#actions-on-github).

## Still stuck

Open an issue on [GitHub](https://github.com/ianmatson/hush/issues), with what you did, what you expected, and what Hush showed.