Search and events settings

Check that notifications, email and search are keeping up, retry events that failed, and rebuild the search index.

“I never got the notification” and “I can’t find that document” often have the same kind of cause: something that should have happened in the background did not. Settings → Search & events shows whether notifications, email and live updates are being delivered, and whether search can find everything that exists — and lets you put it right.

Who can use it#

Permissions

organization.manage

Organization Owner and Organization Admin by default. Every number on the page is for your organization only.

Event delivery#

Every change in UnitX raises an event, and notifications, email and live updates in open browser tabs are delivered from it. If a delivery fails, UnitX tries again several times over about ten minutes. Anything that still cannot be delivered waits here instead of being dropped.

Waiting to deliver: Events raised in the last moment or two that have not been delivered yet. Normally zero or close to it.
Given up on: Events that could not be delivered after repeated attempts.
Oldest still waiting: How long the oldest waiting event has been waiting, or “Nothing waiting”.
Receiving events: The parts of UnitX that receive events, such as notifications and email.

Retry an event that was given up on#

When nothing has failed you see Nothing has been given up on. Otherwise a table lists each event with its type, when it was given up on, which part failed and why, and how many attempts were made.

Read why it failed
The Failed for column names the part that failed — for example email — and its last error.
Fix the cause
For example, correct a misconfigured email setting or wait for an outside service to recover.
Choose Try again
The event is replayed. You see Event replayed and delivered, or Event replayed — it is still being retried if it needs more time.

Note

Replaying re-runs only the parts that never succeeded, so nobody is emailed or notified twice. Events are replayed one at a time; there is no bulk replay.

Search index#

Search reads a copy of your work items, documents and files. The copy is rebuilt from the originals, so a gap here makes things hard to find but never loses data. The table shows, for each type:

In the product: How many of that type exist.
Findable: How many search can currently find.
Not findable: “None”, or a count marked “rebuildable” (fixable here) or “needs reprocessing” (not fixable here).

Rebuild the index#

Open the tab
Go to SettingsSearch & events.
Choose Rebuild
Work items and documents are reindexed from the originals. When it finishes you see how many items were reindexed.

It is safe to rebuild while people are working: rows are updated in place rather than the index being emptied first, so search keeps working throughout.

Note

Files cannot be rebuilt here. A file’s searchable text comes from reading the file itself, which is part of file processing. Missing files show as “needs reprocessing”.

Is an event that was given up on lost?

No. The event and the change that raised it are both still recorded — only the delivery did not happen. That is why the row is still here for you to retry.

Will retrying send duplicate emails?

No. Each part that already delivered is recorded as delivered and skipped.

Someone cannot find a document, but the index shows nothing missing.

Search only shows what each person is allowed to see. Check that they have access to the document. See Search.