Skip to content

LLC: hired agent can't run — heartbeat/trigger returns 'Agent not found or not configured' (heartbeat_scheduler.py:389) #12210

Description

@mrveiss

Summary

A freshly hired agent cannot be triggered to run: POST /api/llc/agents/{agent_id}/heartbeat/trigger returns 500 ValueError: Agent '<id>' not found or not configured (llc/scheduler/heartbeat_scheduler.py:389, via agents.py:126). The hire creates the org node + AGENTS.md, but the agent is not registered/configured with the heartbeat scheduler, so it can never execute.

Repro

  1. POST /api/llc/companies/{id}/agent-hires {"agent_name":"ABR CEO","org_role":"manager", ...} -> 201, returns agent_id; agent appears in /companies/{id}/org-chart (status idle).
  2. POST /api/llc/agents/{agent_id}/heartbeat/trigger -> 500 Agent '<agent_id>' not found or not configured.

Impact

High — the LLC agent-company can define agents but cannot run them. Hiring a CEO/worker produces an org node that is inert; the whole heartbeat/execution model is unreachable through the documented hire→trigger flow.

Likely cause / fix

The hire path doesn't persist the adapter/agent config the scheduler's trigger_manual looks up (or looks it up from a different store). Register the hired agent with the scheduler on hire, or have trigger_manual resolve config from the org node / hire record.

Activity

  1. mrveiss commented on Jul 24, 2026

    @mrveiss
    OwnerAuthor

    Fixed in PR #12250 (merged 2026-07-24). manual trigger resolves hired agent (require_enabled=False); periodic path unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions