Batch data processing
Open Analytics → Batch data processing. Select the Processing agent and an accessible Work conversation belonging to that agent. Use conversation search and More conversations when the desired conversation is on a later page.
Each record retains its own input, result, actual model, and review state. A correctly formatted model response is not proof that its values are factually correct.
Prepare a dataset
- Choose New dataset, enter a name, and choose an operation: Classify records, Extract fields, or Normalize a table.
- Describe what should happen to each record. Keep the instruction specific enough to check against the originals.
- Define the result fields: unique name, value type, whether the field is required, whether it may be empty, and any allowed text values.
- For classification, enter a classification version and the categories, one per line. The required text field
categoryuses those categories. Give a changed classification system a new version. - Add source records with distinct record labels, or paste one record per line and select Add pasted records.
- Select Save dataset before processing.
A dataset supports up to 1,000 records and 128 result fields. The screen initially shows a smaller group; use its additional-record controls to inspect the rest. Text, whole numbers, numbers, and yes/no values are distinct types. “May be empty” is an explicit choice, not permission to omit a required field.
Process only the necessary records
Select Process changed or failed records. Unchanged completed records can retain their existing results; changed inputs or processing configuration require the corresponding new processing and review. A failed record does not discard the other records’ results.
Processing uses the selected agent’s current model configuration and normal budgets. It does not invoke that agent’s tools or write to external systems. Current source and processing restrictions still apply; selecting a conversation does not grant additional permissions.
| State | What to do |
|---|---|
| Waiting or processing | Refresh actual results, or check the original attempt. |
| Provider could not finish this record | Inspect the failure, correct the input or configuration if needed, then explicitly process eligible records. |
| Result not yet confirmed | Check the original processing attempt. Do not create a replacement batch to force another request. The unresolved record is not automatically submitted again. |
| Result format needs correction | Review the instruction, field definitions, and returned result. It cannot be approved as a valid result. |
| Format checked; value still needs review | Compare the proposal with the original and decide whether to approve or reject it. |
An unresolved record does not prevent unrelated eligible changed or failed records from progressing. It also does not become successful merely because another record succeeded.
Review the exact proposed result
Read the original content, proposed values, and actual model shown for each record. Use Approve this result or Reject this result, with a review note when needed.
Results marked uncertain are not available for approval as verified changes. A valid format only checks structure and types. It does not establish identity, correct classification, correct amounts, or completion of an external business action.
Approval applies to the displayed result. If the input, instruction, fields, classification, or model configuration changes, inspect the new result rather than relying on an earlier approval.
If saving, starting processing, or reviewing loses its acknowledgement, use Check the original processing attempt and Refresh actual results. Do not assume the operation was never accepted and repeatedly click it with new data.
Preview and export reviewed changes
Select Review proposed changes to compare before and after values. Only current approved, eligible results enter this preview; skipped records are identified. Inspect the preview, then select Download reviewed changes if appropriate.
The preview and downloaded file do not apply changes to a CRM, database, or other source. Apply reviewed changes only through your separately authorized workflow. Keep the export’s source-record labels when matching it back to originals.
For repeatable calculations without model-based record transformation, see Approved business metrics.