# Signals Watch getting "Failed to Fetch"

**URL:** <https://forum.search-guard.com/t/signals-watch-getting-failed-to-fetch/2091>\
**Category:** Signals Alerting\
**Created:** [February 10, 2021, 6:58pm UTC](https://forum.search-guard.com/t/signals-watch-getting-failed-to-fetch/2091 "2021-02-10T18:58:53Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Doug\_Renze](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/doug_renze/32/720_2.png) [@Doug\_Renze](https://forum.search-guard.com/u/Doug_Renze)\
**Post date:** [February 12, 2021, 1:55pm UTC](https://forum.search-guard.com/t/signals-watch-getting-failed-to-fetch/2091/6 "2021-02-12T13:55:20Z")

</div>

> [@nils](#):
>
> The properties here are null because the watch was executed by manual execution. Thus, it has no schedule in this case.

That makes sense. Thanks for the clarification.

> [@nils](#):
>
> However, looking at the watch definition, I just notice that the watch is missing a trigger definition. Triggers define a schedule when a watch is automatically executed:

I’m defining the trigger definition through the Kibana UI. This is the trigger, as defined in the UI:

![image](https://us1.discourse-cdn.com/flex019/uploads/search_guard/original/1X/ff8b2ce8e58157b100bf19ec3511a9702ca66dd1.png)

However, even when enabled, I’m not seeing anything in the execution history. Note that right now I don’t have an action defined. Does the execution history only show up if there is an action defined?

---

_[View the full topic](https://forum.search-guard.com/t/signals-watch-getting-failed-to-fetch/2091)._