openl Start Trace
openl_start_traceStart asynchronous trace execution for a business rules table by providing input parameters or test ranges, then retrieve execution results with get_trace_nodes.
Instructions
Start trace execution for a table. Trace is asynchronous (returns 202 Accepted). For regular rules: provide inputJson with { params: {...}, runtimeContext?: {...} }. For test tables: use testRanges (e.g. '1-3,5'). After starting, use openl_get_trace_nodes to retrieve results; if you get 409 Conflict, trace is still running—wait and retry.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | Project ID returned by backend. Use the exact 'projectId' value from openl_list_projects() response without modification or reformatting. | |
| tableId | Yes | Table ID to trace (e.g., 'calculatePremium_1234'). Get from openl_list_tables(). | |
| testRanges | No | For test tables: comma-separated ranges (e.g., '1-3,5'). Omit for regular rule/table execution. | |
| fromModule | No | Module name for opened module execution. Usually omit. | |
| inputJson | No | For regular rules: JSON input. Use object with params (required) and runtimeContext (optional). E.g. { params: { age: 25 }, runtimeContext: { lob: 'Auto' } }. | |
| response_format | No | Response format: 'json' for structured data, 'markdown' for human-readable (default), 'markdown_concise' for brief summary (1-2 paragraphs), 'markdown_detailed' for full details with context | markdown |