Runs and troubleshooting
Each run links to the session it created and shows its status. Failed deliveries keep the error needed to trace the problem.
A successful automation handoff creates a regular Hivy session in the configured team. That session is the run record, with the request, agent work, tool calls, result, artifacts, and cost together.
Video placeholder
Compare all three run paths in one video: a connected-app event, a schedule, and an HTTP webhook call. Open each resulting session, expand the agent's work, check the result and cost, then point out any latest-run link.
Find the run in its team
Open the team chosen during setup. Hivy places automated sessions beside the team's other work, where teammates with access can read the context or continue from the result.
Schedule and webhook detail pages show the latest run too. Choose View session when Hivy provides the link; a schedule also reports its latest status and next run time.
Image placeholder
Place one automated session in a readable frame with its team, source, original task or event data, result, work duration, and cost visible.
Start with four checks
- Status
- Enable the trigger or webhook, or make the schedule active.
- Source
- Match the connected account, repository, Slack channel, emoji, or webhook URL to the event you sent.
- Scope
- Check that the agent still belongs to the team and can use the provider connection.
- Instructions
- Read the saved task as the agent would; it needs a clear result and a role for the event data.
If a connected event does not run
Check that the provider connection still works and that the event matches the installed trigger. Look closely at the repository or Slack channel, mention type, and reaction emoji; a disabled trigger ignores every match.
Hivy deduplicates provider deliveries that carry the same delivery identifier, so a provider retry continues the original handoff instead of opening another session.
If a schedule does not run
Check the schedule's status and next run time. You choose daily and weekly times in local time, while Hivy stores and runs them in UTC; a custom interval starts at creation time and may fall between wall-clock boundaries.
Open the schedule for its latest status. If someone moved its agent to another team or archived it, create a new schedule with an agent that belongs to the selected team.
If Hivy rejects an HTTP webhook
- 401: the shared secret is missing or wrong, or the webhook has no configured secret.
- 404: check the URL. Hivy also returns this status after someone disables or deletes the webhook, or archives its agent.
- 413: trim the request body below 256 KB.
A 200 response means Hivy accepted the request for asynchronous processing; check the resulting session for the agent's final result.
Fix the automation or refine the session
Change the automation when future runs need another source, cadence, team, or instruction. A schedule cannot change agents; create a new one when a different agent should run the task. If only one result is wrong, correct it with a follow-up in that session and leave the saved automation alone.
Learn how agent sessions work