Operation Records

Entry, Purpose, and When to Use It

• Entry: after signing in to Routescope, open Operation Records in the account center sidebar.
• Purpose: view Usage Logs and Task Logs in one place to audit call results, token usage, cost, task status, and failure reasons.
• Use it when: confirming whether an API call succeeded, auditing charges, locating a request ID, or checking async task results.

Usage Logs and Task Logs are not separate sidebar entries. They are tabs or sections inside Operation Records.

Usage Logs

Check Consumption

1. Open Operation Records.
2. Enter Usage Logs.
3. Review consumption under the current filters.
4. If consumption looks abnormal, narrow the date range or search by request ID.

Check RPM and TPM

1. In Usage Logs, find RPM and TPM fields.
2. Compare them with request time to identify traffic peaks.
3. If a limit is triggered, check call frequency and token configuration.

Filter by Date

1. Find the date filter.
2. Choose the time range you want to review.
3. Confirm the list and statistics update by date.

Filter by Token Name

1. Find the token name filter.
2. Select or enter the target token name.
3. Review records produced by that token.

Filter by Model Name

1. Find the model name filter.
2. Enter or select the target model.
3. Review request records, input/output, and cost for that model.

Filter by Group

1. Find the group filter.
2. Select the target group.
3. Review usage records and consumption under that group.

Query by Request ID

1. Copy the request ID from code logs, error messages, or response metadata.
2. Paste it into the request ID search box in Usage Logs.
3. Query and expand the single request details.

Request ID is the most direct way to troubleshoot one abnormal call.

View Input and Output

1. Find the target request in the list.
2. Expand request details.
3. Review input and output content.
4. If sensitive content is hidden or incomplete, follow the actual page display.

View Cost

1. Expand the target request.
2. Review cost, token usage, and billing-related fields.
3. If cost differs from expectation, check model name, input length, output length, and group.

View Request Details

1. Open request details for the target record.
2. Review status, duration, model, token, group, input/output, and error information.
3. Use details to decide whether the issue is caused by parameters, permission, balance, or model response.

Task Logs

When Task Logs Apply

Task logs are used for async task records. Image, audio, video, and other tasks that require waiting for results usually need to be checked in Task Logs.

Check Task Status

1. In Operation Records, enter Task Logs.
2. Review the status field in the task list.
3. Pay attention to running, succeeded, and failed states. Exact names follow the page display.

Filter Task Records

1. Use filters on the page to narrow the records.
2. Filter by date, task type, status, or other visible fields.
3. If you have a task ID, use it first.

View Task Result

1. Find the completed task.
2. Open details or result entry.
3. Review the generated result, result URL, or output shown on the page.

View Failure Reason

1. Find the failed task.
2. Expand task details.
3. Review error information or failure reason.
4. Use the reason to adjust input in Playground or the matching API reference.

FAQ

Why can I not find async task results in Usage Logs?

Async task results are usually shown in Task Logs inside Operation Records, where you can review result, status, and failure reason.

Why can I not find a request?

Confirm the date range first, then narrow filters by token name, model name, group, or request ID.