> For the complete documentation index, see [llms.txt](https://gitbook.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.tryprotege.com/event-feed.md).

# Operate

## What this is

The Event Feed is the fastest place to confirm whether Hookshot™ saw an incoming event and how Proteges responded to it.

## When to use it

Use Event Feed when:

* You are testing a new Protege
* You suspect a trigger is not firing
* You need to know whether Hookshot saw the event at all

## What you need first

* A connected integration or schedule
* A Protege expected to respond to an event

## Steps

### 1. Look for the event

Find the incoming task you expected from the provider.

The feed can include external app events, scheduled activity, and run-related entries. Start by confirming the source, timestamp, and any linked Protege.

### 2. Check the Protege status

You may see:

* `ran`
* `dispatching`
* `skipped`
* `unevaluated`

### 3. Use the status as a next action

* If you see `ran`, move to Audit to inspect the actual run result.
* If you see `dispatching`, give the workflow a moment and then recheck.
* If you see `skipped`, review whether the Protege should have acted on that event.
* If you see `unevaluated`, review whether the event path and setup are complete.

### 4. Open related runs

When a feed item has a related run, use it to jump into Audit. Event Feed tells you whether Hookshot saw and routed the signal; Audit tells you what happened during execution.

{% hint style="info" %}
If you see `ran`, it means Hookshot executed the Protege. Do `Audit` next to inspect the result.
{% endhint %}

{% hint style="warning" %}
If you see `skipped`, it means Hookshot saw the event but chose not to run the Protege. Do `review trigger setup and Protege logic` next.
{% endhint %}

## How to verify

### You’re done when...

* The expected event appears
* The expected Protege is associated with it
* You understand which next step belongs to the status you see
* Any related run can be opened in Audit

## Common failures

* No event appears at all
* The wrong Protege is associated with the event
* The same event path is too noisy
* A user jumps to Audit before confirming the event arrived
* A scheduled workflow is checked before the schedule has actually fired

## Next step

* [Audit](/event-feed/audit.md)
* [Work Hub](/event-feed/work-hub.md)
* [Troubleshooting](/event-feed/troubleshooting.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gitbook.tryprotege.com/event-feed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.