Skip to content

Add internal cross-links for agent scheduling, monitoring, and triggers #176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rachaelrenk wants to merge 1 commit into from
Closed

Add internal cross-links for agent scheduling, monitoring, and triggers #176

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/agent-platform/cloud-agents/agents.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ When a team is over its plan limit (for example, after downgrading), the extra a

* **Agents page** - The Agents page in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/) is where teams view, create, edit, and delete cloud agents.
* **Agent picker** - Forms that start a new run or schedule include an **Agent** dropdown. **Quick run** is the default (runs execute as the calling user); picking a cloud agent runs as the cloud agent instead.
* **Run filters and detail** - The Runs view lets you filter by cloud agent, and individual run detail pages show which agent executed the run.
* **Run filters and detail** - The [Runs view](/agent-platform/cloud-agents/managing-cloud-agents/) lets you filter by cloud agent, and [individual run detail pages](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) show which agent executed the run.
* **Admin Panel** - Billing usage in the [Admin Panel](/knowledge-and-collaboration/admin-panel/) attributes credits consumed by cloud agent runs to the team rather than to a person.

## Related pages
Expand Down
4 changes: 2 additions & 2 deletions src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -281,7 +281,7 @@ Each scheduled run behaves like a standard cloud agent run, with a few important
* Runs execute automatically without human intervention.
* All usage is billed to the team’s shared credit balance.

If a scheduled run fails, it does not block future runs. Each execution is independent. Use the [API error reference](/reference/api-and-sdk/troubleshooting/errors/) to interpret any returned error code.
If a scheduled run fails, it does not block future runs. Each execution is independent. Use the [API error reference](/reference/api-and-sdk/troubleshooting/errors/) to interpret any returned error code. To review what a scheduled run did, use the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) to find the run by status or trigger, then open the session with [cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) to inspect the prompt, commands, logs, and output.

### Permissions and responsibility

Expand All @@ -300,6 +300,6 @@ Carefully review prompts and schedules before deploying them broadly, especially

Scheduled Agents are best when work should happen on a predictable cadence.

If you want an agent to run in response to an event, such as a Slack mention, PR update, or issue change, use triggered cloud agents instead.
If you want an agent to run in response to an event, such as a Slack mention, PR update, or issue change, use [triggered cloud agents](/agent-platform/cloud-agents/integrations/) instead.

Many teams use both together: triggers for reactive workflows, and Scheduled Agents for proactive maintenance.
Loading