# Record Guide

How to read run records and metrics is the same as in the SaaS edition ([Record Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/saas/project/guide/record-guide.md), [Records and metrics](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/saas/project/concepts/records-and-metrics.md)). This page sets out what differs in the Marketplace edition.

## Where to look

**There are four places to look** (Workflow history exists only for workflows).

- **Overview** — The current state and the indicators for the period you choose. How they are counted is under “[How the metrics are counted](#how-the-metrics-are-counted)”
- **Execution history** — The list of executions. The “Trigger” column shows what started each one (a sweep, for example). The result filter has “**Run ended (completion not measured)**”. Open one to see its execution record
- **Workflow history** — The list of cases. “**Case details**” on a row opens the case screen (Progress, Settings and files, Records) ([Case Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/guide/case-guide.md))
- **Action needed** — Things that need a person (next section)

**Reviews across projects are in “Inbox” ＞ “Review requests” on the left** ([Review Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/guide/review-guide.md)).

**Decide who looks at failed runs and at reviews that stay undecided, and how often.** For example, an owner checks “Action needed” each morning and prompts the reviewers of any reviews that remain.

## Clearing what needs a person

**“Action needed” lists each thing that needs a person, one per row.** It needs no setup. It is built from review requests, runs, and sweep records, from their state at that moment. There are eight kinds.

| Kind                    | What is listed                                                                                                                                                                                                                                                                                                           | Who is responsible                                    |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------- |
| **Awaiting approval**   | A review request that is not yet decided                                                                                                                                                                                                                                                                                 | The reviewer                                          |
| **Overdue**             | A review request past its deadline and still undecided. **It is not decided automatically after the deadline** ([Review Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/guide/review-guide.md))                                                                                      | The reviewer                                          |
| **Waiting on external** | A review waiting on an external condition whose connector state cannot be read before the review deadline. Once the deadline passes it appears as “Overdue”. The reason is shown on the case screen ([Review Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/guide/review-guide.md)) | The reviewer                                          |
| **Failed**              | In an open case, the agent in the current step failed and no review request is open                                                                                                                                                                                                                                      | The owner                                             |
| **Awaiting rework**     | Sent back, and the step it returns to has not started yet                                                                                                                                                                                                                                                                | The reviewer of the review request that was sent back |
| **Sweep failed**        | In a cycle, the latest sweep of a placement ended in a failure result (“Failed (agent report)”, “Failed”, “Denied by rule”, “Timed out”)                                                                                                                                                                                 | The owner                                             |
| **Past deadline (run)** | A case that is not finished after its deadline                                                                                                                                                                                                                                                                           | The owner                                             |
| **Stalled**             | A running case that has not progressed after the “hours before a run counts as stalled” (cases awaiting review, and cases for which cancellation was requested, are not included)                                                                                                                                        | The owner                                             |

**The list is ordered by priority (P1 to P4).** Priority is decided mechanically and cannot be changed by hand. Within the same priority, items with the nearest deadline and the oldest items come first.

- **P1** — Overdue, waiting on external, past deadline (run)
- **P2** — Failed, sweep failed, stalled, and reviews awaiting approval with less than 24 hours to their deadline
- **P3** — Other reviews awaiting approval, and awaiting rework
- **P4** — Reviews awaiting approval with no deadline

**Up to 100 rows are listed at a time.** You can filter by the kinds above.

### Acting on several rows

**Selecting rows shows “Bulk actions”.** The actions are as follows. Each is applied to the selected rows it applies to (the number of rows it does not apply to is shown; “Reassign approvers” alone works per case, as the table below shows). In the Marketplace edition:

| Action                                 | In the Marketplace edition                                                                                                                                                                                                 |
| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Approve**, **Reject**, **Send back** | Open the review request and decide one at a time, based on the version you checked. Approval applies to reviews awaiting approval and overdue ones; a person cannot advance a row that is waiting on external              |
| **Extend deadline**                    | Applies to review requests. Enter a new deadline (a date and time later than now)                                                                                                                                          |
| **Reassign approvers**                 | Applies to review requests of cases. **Reassigning is done per case, and all undecided review requests of that case are replaced, including rows you did not select.** Choose the new reviewers from the project's members |

**Someone who opened the project only through the organization operations role can use only “Extend deadline” and “Reassign approvers”.**

**The result is shown per row.** It is “Done”, “Already decided” (someone else decided first), “No permission”, “Conflict (content was updated)”, “Decide individually”, “Not found”, “Failed”, and so on. For a row that says “Decide individually”, open the review request and decide it by itself.

Where in the UI The project's “Action needed” tab. Bulk actions appear when you select rows

### Deadlines and stalls (workflows)

**A case can have a deadline.** Passing the deadline does **not stop the case.** It appears under “Past deadline (run)” in “Action needed”.

- **Default deadline** — Under Settings > “Execution rules”, choose “Default run deadline (hours after start)”. Each case started afterwards gets a deadline that many hours after its start. The default is “None”
- **Deadline for one case** — Set, change, or clear it on the case screen ([Case Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/guide/case-guide.md))

**A running case that is not progressing appears in “Action needed” as “Stalled”** (cases awaiting review, and cases for which cancellation was requested, are not included; a case past its deadline appears under “Past deadline (run)” instead). The “hours before a run counts as stalled” is counted from when the last step finished (or from the start, if none has finished). The default is 24 hours.

Where in the UI Settings > “Execution rules”: “Default run deadline (hours after start)” and “Hours before a run counts as stalled” (only the owner can change them, for workflows)

## Reading a single run

A run record shows “**Runtime image**” in addition to the SaaS edition's items (under “Run info” ＞ “Settings at run time”). It is the container image of the registered agent that ran in that execution. In a workflow it shows the image digest an administrator certified (`sha256:…`); in a cycle, the registry, image name and tag.

From a workflow's run record or Workflow history, “**Case details**” opens the case screen. The versions of settings and artifacts are seen on the case screen ([Case Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/guide/case-guide.md)).

**What “View current settings” in the heading shows differs from the SaaS edition.** For a registered agent whose contract is registered and can be read, it shows a summary of the contract (“Effect on external systems” with the execution limit, “Files”, “Outputs” and “Connectors”). For an agent with no contract, or one whose contract cannot be read (such as an agent used in chat that you place only in a cycle), it shows “This information is not available yet”. In neither case is “Edit Agent” shown.

## Opening the body leaves a reason on record

**The body of a step's execution (its request and response) is opened by giving a reason.** To open it, enter a reason (up to 300 characters) on the execution record screen. Only members who opened it with a reason can read the body (a reason stays valid for 30 minutes; after that, enter it again). Who opened it, and the reason, are kept in the record. **A person who opened the project only through the organization operations role cannot open the body.**

## When it could not be launched

When a registered agent could not be launched, the run record shows the reason. Here are the reasons that often appear, and what to fix.

| Reason                                                                 | What to fix                                                                                                                                                                                                         |
| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The Agent is not certified for this project's execution rules          | Compare the project's basic rules with the agent's “Supported run rules” ([Execution Rules and Traffic Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/guide/control-guide.md)) |
| The Agent's certification details were incomplete                      | An administrator registers the agent's certification again                                                                                                                                                          |
| The Agent contract was invalid                                         | An administrator fixes the agent's contract                                                                                                                                                                         |
| The linked service selected for the step was unavailable               | An owner checks the connectors chosen in the step settings and the connectors in Settings                                                                                                                           |
| The approved version of the linked service changed or was not found    | The connector's settings changed. An owner chooses the connector again in the step settings                                                                                                                         |
| The credentials for the linked service were missing or no longer valid | Reconnect the connector                                                                                                                                                                                             |
| The Agent image to run could not be identified                         | An administrator checks the agent's image settings (registry, image name) (mainly cycles)                                                                                                                           |
| Environment variables set by the administrator conflicted              | An administrator removes names the platform settles from the agent's environment variables (cycles)                                                                                                                 |
| The step's environment variables included a name that cannot be used   | An owner removes the name that cannot be used from that step's environment variables (cycles)                                                                                                                       |

## The cycle result “Run ended (completion not measured)”

Even when a cycle's registered agent finishes its processing and exits normally, **the platform cannot judge whether it did its job.** The result of such an execution is “**Run ended (completion not measured)**”.

- **It is counted as neither a success nor a failure.** It is not part of the denominator of metrics such as the agent completion rate. The Overview metrics show the number with “Completion not measured” separately
- The result filter in Execution history has “**Run ended (completion not measured)**”
- What the execution did is checked in that execution's conversation
- The result notice ([Connection Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/saas/project/guide/connection-guide.md)) is not sent. It is sent only for executions in which the agent reported completion

If the agent is built to report whether it completed (the SDK's `report_completion`), it is recorded with the same seven results as in the SaaS edition. How to build it is in [Your First Agent](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/develop/quickstart/quickstart-sdk.md#report-completion).

When the agent's process ends abnormally, the Pod disappears, or the execution limit is exceeded, any report from the agent is not used, and it is recorded as failed or timed out.

## Stopping a cycle execution

A cycle execution in progress can be stopped with “**Stop**” in its run record. It is shown **to owners, operators and people with the organization operations role**. It can be used on executions waiting to start and on executions that are running.

**Stopping from the conversation screen does not stop a cycle execution.** Use “Stop” in the run record.

## How the metrics are counted

The metrics are counted as in the SaaS edition ([Run Results Reference](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/saas/project/reference/results-ref.md)). The denominator is, in a workflow, the executions of registered agents placed on steps (excluding review steps and steps passed through), and in a cycle, the executions of registered agents (both periodic sweeps and runs started by webhook). “Run ended (completion not measured)” is not part of the denominator.

## Records (audit trail)

In addition to the SaaS edition's events, Records (audit trail) keeps “**Case Config Changed**”. It is the record made when the case settings are saved as a new version. Events about consulting on improvements, email and the joining of parallel lanes do not exist in the Marketplace edition. The branch events “Branch decided” and “Branch asked a person” are kept as in the SaaS edition.

## Revisiting it from the track record

Of “Revisiting it from the track record” in the SaaS edition's Record Guide, **the feature for consulting the AI on improvements and carrying them out does not exist.** To revisit, read the run records and the track record of reviews, and choose where to fix as follows.

| What you see                                | What to fix                                                                                                                                                                                                                                                                        |
| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The values in the step settings do not fit  | An owner fixes the step settings                                                                                                                                                                                                                                                   |
| The same correction is made at every review | Consult an administrator about the contract's defaults, and the developer about how the agent is built                                                                                                                                                                             |
| Failures and timeouts continue              | Have the developer check how the agent is built and its execution limit, and whoever operates the environment check the traffic allowed ([Execution Rules and Traffic Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/guide/control-guide.md)) |
| “Not allowed by rules” continues            | Compare the project's basic rules with the agent's “Supported run rules”                                                                                                                                                                                                           |

## Easy to get wrong

- **Thinking that a result of “Completed” means the business went well.** “Completed” only means the agent finished it as completed. Check by the artifact's contents
- **Reading a cycle's “Run ended (completion not measured)” as a failure.** It counts as neither success nor failure. Check what it did in that execution's conversation
- **Thinking that stopping from the chat screen stops a cycle execution.** Use “Stop” on the execution record
- **Thinking you can approve, reject, or send back rows in “Action needed” in bulk.** Decide review requests for cases one at a time
- **Thinking an overdue review is decided automatically.** It is not. It appears in “Action needed” as overdue and waits for the reviewer

## What to read next

- [Review Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/guide/review-guide.md) — How to decide a review request
- [Case Guide](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/guide/case-guide.md) — The case screen, and versions of settings and artifacts
- [Run Results Reference](https://developers.fd.agenticstar.tm.softbank.jp/en/docs/marketplace/project/reference/results-ref.md) — The result words and the completion-rate formula
