Trace Workflow
AI-generatedOverview
The Handit Tracing node collects detailed workflow execution data and sends it to the Handit API for tracing and analysis. It is designed to capture node types, input sources, parameters, and outputs within a workflow, enhancing traceability and debugging capabilities. This node is useful for monitoring complex workflows, auditing execution paths, and integrating with external tracing systems like Handit.
Use Case Examples
- A user wants to monitor the execution of an AI-driven workflow by capturing each node's input and output data and sending it to Handit for visualization and analysis.
- A developer needs to audit workflow executions to ensure data integrity and trace parameter changes across nodes, using the Handit Tracing node to send structured workflow data to an external API.
Properties
| Name | Meaning |
|---|---|
| Agent Name | Name of the agent for tracing, used to identify the source of the trace data. |
| Workflow Structure | A JSON object defining the workflow structure, including node types and their dependencies. This structure is used to capture parameters and trace data accurately. |
| API URL | Custom API endpoint URL to which the workflow trace data is sent. If left empty, the default Handit API endpoint is used. |
Output
JSON
success- Indicates whether the data was sent successfully.message- A message describing the result of the data send operation.response- The response received from the Handit API after sending the data.data- The workflow trace data that was sent to the API.
Dependencies
- Handit API credentials (API token) required for authentication.
Troubleshooting
- Invalid JSON in the 'Workflow Structure' property will cause an error; ensure the JSON is correctly formatted.
- Missing or invalid Handit API credentials will prevent data submission; verify that the API token is correctly configured.
- Errors during data processing or HTTP request failures will be reported with error messages; check network connectivity and API endpoint correctness.