Script History
Overview
Every script execution in ScriptForge is logged automatically. The Execution History section shows a chronological record of all script runs across every feature — console executions, listener firings, scheduled job runs, workflow rule evaluations, and more.
What Gets Logged
Each execution record captures:
| Field | Description |
|---|---|
| Timestamp | When the script started executing |
| Feature | Which feature triggered it (Console, Listener, Scheduled Job, Workflow, etc.) |
| Script Name | The name of the listener/job/rule, or "Console" for ad-hoc runs |
| Status | Success, Error, or Timeout |
| Duration | How long execution took (milliseconds) |
| Output | Console log output and return value |
| Error | Error message and stack trace (if failed) |
| Context | Trigger event details (issue key, event type, user) |
Viewing History
- Navigate to Apps → ScriptForge
- Click Execution History in the left sidebar
- Browse the list sorted by most recent first
Filtering
You can filter execution history by:
- Feature type — Show only listener runs, only console runs, etc.
- Status — Show only errors, only successes
- Date range — Narrow to a specific time period
- Search — Find by script name or output content
Use Cases
- Debugging: When a listener isn't doing what you expect, check its execution logs to see the output and any errors
- Auditing: Track who ran what and when for compliance purposes
- Performance: Identify slow-running scripts by sorting by duration
- Error tracking: Quickly find failed executions and their stack traces
Retention
Execution history is stored in Forge SQL. Older entries may be pruned based on storage limits. For long-term auditing, consider exporting log data periodically.