Diagnose Repeated Job Failures with Agent Data
Jobs failing repeatedly? Know immediately if it's an agent problem.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
List Pipeline Agents
Tool to list connected agents for an organization. use after confirming the organization slug. supports optional filtering and pagination.
Why this helps
CI job fails intermittently but you can't tell if it's an agent issue without manual checking - leads to wild guessing and wasted debugging
- Agent inventory checked automatically on failures
- Capacity and health issues identified immediately
- Root cause narrowed before deep debugging
- Less time wasted on wrong solutions
Setup
Build it in a few focused steps.
- 1Connect Linear and Buildkite to Notis
- 2Create automation: When an issue is updated about a job failing repeatedly, list all Buildkite agents and their current status and load
- 3Select Issue Updated as the trigger
- 4Choose your notification channel
- 5Test by updating an issue about a failing job and confirm agent status appears
Questions about this workflow
Can this detect which agent a job is running on?
This shows all agents and their status. Integration with Buildkite logs can pinpoint the specific agent for a job.
Does it distinguish between 'no agents available' and 'agent overloaded'?
Yes, the status includes capacity and load information for each agent
Can I automatically trigger a job re-run on a different agent?
This automation provides diagnostic data. Job management and retries are separate steps.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Buildkite. A trigger fires from one place; an action lands in another.
Linear triggers
Buildkite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Current Access Token
Tool to retrieve the authenticated api access token details. use when you need to confirm the validity and scopes of the current api token.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Meta
Tool to retrieve metadata about the buildkite api. use when you need to fetch webhook ip addresses for firewall or security configurations.
Comment Received Trigger
Triggered when a comment is received.
List Pipeline Agents
Tool to list connected agents for an organization. use after confirming the organization slug. supports optional filtering and pagination.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Buildkite, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Buildkite.