Activity

Activity is the record of every event that reached Loha — a push, a pull request, a tag, a manual run — and what Loha decided to do about it.

It answers one question that nothing else can: "I pushed, and nothing happened. Why?"

A build that runs is visible in Builds. An event that produced no build is only visible here.

Where to find it

Scope	Where
Whole workspace	Activity in the sidebar, beside Builds
One repository	the repository's Activity tab
One trigger	the trigger's Activity tab

Start at the workspace view when the question is "is Loha receiving anything at all?" — that is not something you can answer by opening repositories one at a time.

What a row tells you

Column	Meaning
Received	When the event reached Loha
Outcome	What was decided — see below
Event	The event kind and its branch or tag, e.g. push · main
Trigger	Which trigger the event was delivered to
Reason	Why that outcome, in words
Build	A link, when the event produced one

Outcomes

Outcome	What happened
Built	The event matched, and a build started.
Skipped	The event arrived and was deliberately not built. The reason says which rule excluded it.
Rejected	The delivery failed verification — usually a webhook secret that does not match.
Duplicate	Your Git host delivered the same event twice; Loha reused the first build rather than making a second.
Processing	Received, not yet decided.
Failed	Loha could not finish processing the event after several attempts. Rare, and worth reporting.

Skipped is not an error

Most skips are correct — a push to a branch you did not ask to build. The row exists so that a deliberate skip and a broken trigger stop looking identical.

The reason column

The reason is written by the part of Loha that made the decision, and shown to you unchanged:

Branch feat/cache does not match branches filter

That tells you which rule applied and what to change: either widen the trigger's branch filter, or switch the trigger to follow your pipeline file.

An empty Activity list

An empty list means Loha has received nothing — which is different from "everything was skipped".

If you have pushed since connecting the repository and see nothing here, the webhook is almost certainly not wired up. Check the repository page: it will say "Not building — webhook not wired" and offer to fix it. See Repositories.

What is not shown

Activity deliberately does not show the raw webhook payload. Those bodies carry commit messages and author email addresses, and Loha shows the extracted event summary instead — the kind, branch, commit and tag.

Related

• Triggers: what decides whether an event builds
• Builds: the runs that events produced
• Repositories: connecting a repository and wiring its webhook