Execution History

Execution History tracks every script you run in LMDA Composer, allowing you to review past executions and reload scripts.

Accessing History

Method	Action
Sidebar	Click History tab in the right sidebar
Keyboard	Ctrl+B to toggle sidebar
Command Palette	Press Cmd+Shift+P and type “History”

---

History Entry Details

Each execution entry shows:

Field	Description
Status	Success or Error
Name	Tab or module name
Timestamp	When it was executed
Duration	How long it took
Mode	Execution mode used
Language	Groovy or PowerShell
Collector	Which collector ran it
Device	Target device (if set)
Output Preview	First few lines of output

---

Viewing Full Details

Click View on an entry to see:

Execution Summary

• Complete status and timing
• Portal and collector info
• Device context
• Execution mode and language

Script Content

The complete script that was executed:

• Syntax highlighted
• Read-only view
• Copy functionality

Full Output

Complete output from the execution:

• Raw text output
• Scroll for large outputs
• Copy entire output

Parsed Results

For AD/Collection modes:

• Parsed instance/datapoint data
• Same format as Output Panel

---

Reloading Scripts

Load to Editor

Click Load on a history entry to:

1. Open a new tab

2. Populate with the historical script

3. Set language and mode automatically

4. Ready for editing and re-running

Portal Mismatch Warning

If the history entry is from a different portal:

Portal Mismatch

A warning dialog appears with options:

• Switch Portal: Change to the original portal
• Load Anyway: Load as freeform script
• Cancel: Abort the load

Module Binding

Historical scripts from modules:

• Can restore module binding if portal matches
• Falls back to freeform if unavailable

---

History Management

History Limit

Configure the maximum history entries:

1. Open Settings (Ctrl+,)

2. Find “History Size”

3. Set desired limit (10-500, default is 50)

4. Oldest entries removed when limit exceeded

Clearing History

To clear all history:

1. Click Clear button in panel
2. Confirm the action
3. All entries removed permanently

Note

Individual entries cannot be deleted separately. Use the clear function or let them naturally expire based on the history limit.

---

History Use Cases

• Debugging — Find a working historical execution, compare with current script, identify what changed
• Recovering Scripts — If you lose script content, find the last execution and load it back
• Performance Analysis — Compare execution durations across runs to identify slow executions
• Auditing — Track what was executed, check timestamps, document actions taken

---

What’s Stored

Data	Stored?
Script content	Yes
Output	Yes
Collector info	Yes
Device info	Yes
Timestamp	Yes
Duration	Yes
Tab/module name	Yes
Portal binding	Yes

Storage Location

History is stored:

• In browser local storage
• Per-browser (not synced)
• Persists across sessions
• Subject to size limits

Storage Limits

Large outputs or many entries may impact browser storage. Very large histories may trigger automatic cleanup.

---

History Panel Actions

Action	Icon	Description
View	Eye	See full execution details
Load	Arrow	Load script to editor
Copy	Clipboard	Copy script content

---

Best Practices

• Regular Review — Periodically review history, export important scripts, document significant executions
• Before Clearing — Review important entries and save scripts you want to keep before clearing
• Learn from History — Review successful patterns and past decisions to improve future scripts

---

Privacy Considerations

History may contain:

• Device information
• Property values (from token substitution)
• API responses (if printed)
• Sensitive configuration data

Clear history when:

• Switching between projects
• Working on sensitive systems
• Sharing the browser/computer

---

Next Steps

Settings Configure LMDA Composer appearance, defaults, and behavior.