Authorization configuration being corrected.
Contains the authorization implementation details for a specific role that failed compilation and requires correction.
Timestamp when the event was created.
ISO 8601 formatted date-time string indicating when this event was emitted by the system. This timestamp is crucial for event ordering, performance analysis, and debugging the agent workflow execution timeline.
Format: "YYYY-MM-DDTHH:mm:ss.sssZ" (e.g., "2024-01-15T14:30:45.123Z")
A unique identifier for the event.
Function calling trial statistics for the operation.
Records the complete trial history of function calling attempts, tracking total executions, successful completions, consent requests, validation failures, and invalid JSON responses. These metrics reveal the reliability and quality of AI agent autonomous operation with tool usage.
Trial statistics are critical for identifying operations where agents struggle with tool interfaces, generate invalid outputs, or require multiple correction attempts through self-healing spiral loops. High failure rates indicate opportunities for system prompt optimization or tool interface improvements.
The compilation failure details that triggered the correction process.
Contains the specific compilation error information describing what validation errors were detected in the authorization implementation code (providers, payloads, decorators). This includes error messages, file locations, type issues, or other compilation problems that prevented successful validation.
Iteration number of the requirements analysis this correction was performed for.
Indicates which version of the requirements analysis this authorization correction reflects. This step number ensures that correction efforts are aligned with the current requirements and helps track the evolution of code quality as validation feedback is incorporated.
Detailed token usage metrics for the operation.
Contains comprehensive token consumption data including total usage, input token breakdown with cache hit rates, and output token categorization by generation type (reasoning, predictions). This component-level tracking enables precise cost analysis and identification of operations that benefit most from prompt caching or require optimization.
Token usage directly translates to operational costs, making this metric essential for understanding the financial implications of different operation types and guiding resource allocation decisions.
Unique identifier for the event type.
A literal string that discriminates between different event types in the AutoBE system. This field enables TypeScript's discriminated union feature, allowing type-safe event handling through switch statements or conditional checks.
Examples: "analyzeWrite", "prismaSchema", "interfaceOperation", "testScenario"
Event fired during the correction phase of authorization implementation.
This event occurs when the TypeScript compiler detects issues in the generated authorization code and the Realize agent attempts to correct these compilation errors. The correction process involves analyzing compiler feedback and regenerating the authorization components to resolve type errors, syntax issues, or other validation problems.
Author
Michael