Skip to Content
Tares

Where do I see whether the trigger for failed deploys fired and which run it woke?

Tares shows every firing of your failed deploys trigger on the trigger’s page and under Firings in the console. Activity shows the firing and the run it woke as one thread, and the agent’s Runs lists every run. If the trigger did not fire, check that its sources and filters match the events that arrived.

How it works

A trigger evaluates as events arrive on the sources it watches. When its filters and condition match, it fires and wakes the agent subscribed to it. Tares records each step in a place you can open:

  • The trigger’s page and Firings list each time the failed deploys trigger fired.
  • Activity, under Setup, then Advanced setup, shows the firing and the run it woke as one thread.
  • Agents, then the agent, then Runs has every run that agent has made, including the one the firing started.
  • Explore shows the events on the service’s timeline, so you can compare them with what the trigger watches.

The Build an AI SRE guide walks through the same chain with its incident trigger and the incident-first-look agent. Your failed deploys trigger uses the same pages.

Set it up

You do not need to configure anything new. Follow the trail from the trigger to the run.

  1. Open the console. On a local Tares, start it and go to http://127.0.0.1:8787.
tares up
  1. Open Triggers and pick failed deploys. Its page lists its firings. The same firings appear under Firings. A firing with a recent time means the trigger matched an event.
  2. Open Setup, then Advanced setup, then Activity. Find the firing. Activity shows it together with the run it woke, so you can see which run belongs to which firing.
  3. Open Agents, choose the agent subscribed to the trigger, and open Runs. Open the run that matches the firing to see what the agent did.
  4. If the agent recorded a finding, look for it on the project’s Overview under What the agents found. The same finding sits on the service’s timeline in Explore.
  5. If the trigger shows no firing, check what it watches:
    • Open the trigger and read its sources. Confirm the source that carries your deploy events is in the list.
    • Read its filters and its condition, including the window. Confirm the field names and values match the events that arrived.
    • Open Explore for the service and look at the events on the timeline. Compare their fields with the filters.
  6. If the events are missing from the timeline, the problem is upstream of the trigger. Check the source that should be receiving them.

What you get

  • A clear answer to whether the failed deploys trigger fired, from its own page or from Firings.
  • The run each firing woke, shown next to the firing in Activity.
  • The full history of that agent’s runs under Runs.
  • The agent’s finding on the timeline, if it wrote one, so you can see the conclusion without opening the run.
  • A short checklist when nothing fired: the trigger’s sources, its filters and the events on the timeline.

When something else fits

  • If you want to investigate the evidence yourself instead of tracing the trigger, connect an MCP client and ask it to read the service’s timeline. The Build an AI SRE guide shows how.
  • If the trigger fired but the wrong agent or channel was woken, review which agent, webhook or Slack channel the trigger is set to wake.

Still stuck? Get help

Last updated on
Quickstart