Overview

Every time a tool or function runs in Sigma Domain, the execution is recorded. You can look up past executions to see what was run, what parameters were used, and what the results were.

What Gets Recorded

Each tool execution record includes:

• Tool name - Which function was executed
• Parameters - The input values sent to the function
• Result - The response from the API/service
• Status - Success or failure
• Timestamp - When the execution occurred
• Error details - If it failed, what went wrong
• Duration - How long the execution took
• Associated job - If it was part of a workflow

Viewing Execution History

In Chat

Ask the AI to look up your history:

• "Show my recent tool executions"
• "What tools have I used today?"
• "Show the last time I ran the Twilio SMS function"

In a Job Context

When viewing a job artifact:

• Each completed step shows its execution result
• Click on a step to see full details
• Failed steps show error messages and retry attempts

Understanding Execution Results

Successful Execution

• Shows the API response data
• May include formatted output (tables, lists)
• Result data is available for follow-up queries

Failed Execution

Each failure includes:

• Error message - What went wrong
• HTTP status code - The API's response code (e.g., 401 Unauthorized, 422 Validation Error)
• Missing parameters - If required fields weren't provided
• Retry count - How many times the system attempted the execution

Common Error Codes

Code	Meaning	What to Do
401	Unauthorized	Check your API key or OAuth token
403	Forbidden	Your key may lack required permissions
404	Not Found	The endpoint or resource doesn't exist
422	Validation Error	Required parameters are missing or invalid
429	Rate Limited	Wait and try again later
500	Server Error	The external API had an internal error

Querying Your Execution Data

Your execution history is stored in your personal database schema. You can query it:

Recent Executions

"Show my last 10 tool executions"

Filter by Tool

"Show all executions of the Twilio SMS function"

Filter by Status

"Show all failed executions this week"

Filter by Date

"What tools did I run yesterday?"

Execution History and Jobs

Job Step Tracking

• Each job step that runs a tool creates an execution record
• The record links back to the job via a workflow_id
• You can see which job triggered each execution

Retry Tracking

• When a step retries, each attempt is recorded
• The attempts field shows a list of all attempts with timestamps
• Useful for debugging intermittent failures

Data Retention

• Execution history is stored in your personal database schema
• Records persist until you explicitly delete them
• You can export execution data as CSV or JSON

Troubleshooting with History

Debugging a Failed Tool

1. Ask: "Show the last execution of [tool name]"
2. Check the error message and HTTP status code
3. Verify the parameters that were sent
4. Compare with a previous successful execution

Finding What Changed

1. Ask: "Compare my last two executions of [tool name]"
2. Look for differences in parameters or error messages
3. Check if authentication credentials have expired

Reporting Issues

When reporting a tool issue, include:

• The execution timestamp
• The tool name and parameters used
• The error message received
• Whether it worked previously