---
title: "InfoOps Report Workflow"
description: "How Y2 researches a profile, creates its report, and recovers from failures."
canonical: https://y2.dev/docs/workflows/
---

# InfoOps Report Workflow

How Y2 researches a profile, creates its report, and recovers from failures.

A profile defines a recurring research task. Each run collects sources, writes one report, adds intelligence data, and delivers the result. [Automations](https://y2.dev/docs/automations) are separate tasks that run Agent Y2 on a schedule or after a report.

## How a run starts

Y2 queues a run when:

- An active custom profile is created.
- A paused or canceled profile becomes active.
- An active profile's status or schedule changes.
- The next scheduled time arrives.
- Recovery restarts an eligible failed or interrupted run.

Y2 prevents overlapping runs for the same profile. A pending retry can delay a new start. Creating an active profile starts an initial report and schedules the next regular run.

## Research and synthesis

### Root research

Y2 searches the profile topic through Exa. Time range, topic, result count, and domain restrictions affect the request. The engine checks source freshness before synthesis.

Freshness controls

The engine uses its default freshness rules. Saved **Source Freshness** and **Link Validation** switches do not override those rules. Domain and time-range controls apply directly.

### Child research

With recursion enabled, Y2 proposes two or three subtopics and researches them in parallel. Successful findings and unique sources join the root results. A failed child search does not discard successful research.

One child layer maximum

The editor always enables recursion. Its layer choices run at most one child layer. Set `recursionConfig.enabled: false` through the Profiles API for root-only research.

The engine uses breadth-first research. The saved strategy field does not change that behavior. Research has a 480-second overall budget, with up to 120 seconds reserved for child searches.

### Report synthesis

Y2 combines the research and removes duplicate sources. The combined research input is limited to 35,000 characters. Synthesis also receives:

- The topic and up to 2,000 characters of custom instructions.
- The saved report sections and their guidance.
- Evidence, confidence, and source-citation requirements.
- Branding terminology.
- A summary of up to three prior reports.
- Structured signal requirements and source URLs.

User instructions control presentation. Required report structure and completeness checks still apply. An incomplete report stops before audio and delivery.

## Models and provider routing

The profile editor does not select the report model. Generation can retry a model or use a configured fallback after a supported failure. A profile's `modelConfig.modelId` does not replace the executed model sequence. Temperature and output-token settings still apply.

If subtopic generation fails, Y2 can use prepared child-query templates. Final synthesis must still produce a complete report. Provider routing settings deny data collection through OpenRouter.

## Post-processing and delivery

| Stage      | Behavior                                                                                     |
| ---------- | -------------------------------------------------------------------------------------------- |
| Audio      | Attempts narration when enabled. Failure does not block the report.                          |
| Enrichment | Extracts events, graph information, and incident metadata. This must finish before delivery. |
| Delivery   | Sends the report through each subscription's configured channel.                             |
| Scheduling | Updates delivery state and schedules the next normal run.                                    |

Webhooks contain report status, counts, audio availability, and API links. They do not contain the complete report. See [Webhook delivery](https://y2.dev/docs/delivery/webhooks).

## Failure recovery

Report state is `generating`, `completed`, `failed`, or `canceled`. A run has a 45-minute execution lease. Recovery can extend it once by 30 minutes.

Eligible failures can retry three times, after 5 minutes, 15 minutes, and 1 hour. Recovery resumes the failed step when workflow history is available. Otherwise, it queues a fresh run. After retries end, Y2 repairs the regular schedule.

A current run or pending retry prevents duplicate starts. Check the profile's state before starting another run.

## Configure the implemented workflow

Use [Create a profile](https://y2.dev/docs/profiles/creating) to set the topic, sections, research controls, and delivery. Use [Schedule profile reports](https://y2.dev/docs/profiles/scheduling) to change its cadence.

## API boundary

Use the [Profiles API](https://y2.dev/docs/api/profiles) to create or change a profile. Use the [Reports API](https://y2.dev/docs/api/reports) to read its output. There is no public endpoint for starting an arbitrary internal workflow.

Profile writes require `profiles:write`. Report reads require the corresponding `reports:*` scope.
