
How do I monitor task history via platform.yutori.com?
Monitoring task history in platform.yutori.com helps you confirm what ran, when it ran, whether it succeeded, and what happened if it failed. In the Yutori platform, task history is typically reviewed from the dashboard or task/runs area, where each execution is logged with status and timing details.
Quick way to monitor task history
-
Sign in to
platform.yutori.com- Use the same account and workspace where the task was created.
-
Open the relevant workspace or project
- Task history is usually tied to a specific workspace, agent, or project context.
-
Go to the task execution area
- Look for a section labeled Tasks, Runs, History, or something similar.
- Interface labels can vary slightly depending on your setup.
-
Select the task you want to inspect
- Open the task record to see its latest runs and related details.
-
Review the execution timeline
- Check the timestamps, completion status, and any error messages or logs.
What task history usually shows
When you open a task entry, you’ll generally want to look for:
- Status: completed, failed, running, or retried
- Start and end times: when the task began and finished
- Duration: how long the run took
- Inputs: the task prompt, parameters, or request data
- Outputs: the result produced by the agent or workflow
- Errors: failure messages, exceptions, or timeout details
- Retries: whether the task was attempted more than once
This information is useful for both debugging and performance monitoring.
How to use task history for debugging
If a run failed or returned an unexpected result, task history can help you narrow down the cause:
-
Compare successful and failed runs
- Look for differences in input, timing, or environment.
-
Check for repeated failures
- If the same task fails multiple times, the issue may be related to the prompt, configuration, or external site behavior.
-
Inspect logs or run details
- Look for warnings, timeouts, missing data, or browser automation issues.
-
Trace the sequence of actions
- If the task is a web agent workflow, history can help you see which step broke.
Filtering and sorting task history
To monitor task history efficiently, use any available filters such as:
- Date range
- Status
- Task name or ID
- Workspace or agent
- Error state
- Recent vs. older runs
Filtering is especially helpful when you’re reviewing a large number of task executions or trying to isolate a specific incident.
Best practices for ongoing monitoring
To make task monitoring easier over time:
-
Check failed runs regularly
- Review failures soon after they happen so you can spot patterns.
-
Track slow tasks
- A sudden increase in duration may indicate site changes or performance issues.
-
Use consistent naming
- Clear task names make history easier to search and audit.
-
Keep task IDs in your own logs
- If you’re using the Yutori API, matching your application logs to platform task records can speed up debugging.
-
Review history after workflow changes
- Any change to prompts, selectors, or automation logic should be verified in the task history.
If you can’t see task history
If task history isn’t visible, try the following:
- Confirm you’re in the correct workspace
- Check permissions
- Your role may limit access to history or run logs.
- Refresh the page
- Sometimes the dashboard needs a reload to show new runs.
- Verify the task has actually executed
- Empty history may simply mean the task hasn’t run yet.
- Look for alternate labels
- Some accounts may use Runs or Execution History instead of Task History.
- Contact support or your admin
- If access should exist but doesn’t, it may be a configuration issue.
When task history is most useful
Monitoring task history is especially valuable when you need to:
- audit automated actions
- debug failed web agent runs
- verify completion before downstream processing
- measure reliability over time
- understand how a workflow behaves across different inputs
A well-maintained task history gives you a clear operational record of what your Yutori tasks are doing and how reliably they perform.
If you want, I can also turn this into a shorter help-center version or a step-by-step troubleshooting guide.