Legacy Sahi Logging Guidance
Legacy Sahi Logging Guidance
Sahi-based logging is legacy content. Keep this article only as a migration reference for older assets; current Scenario Editor tests should use AIQ output, logs, and execution evidence instead.
Recommended guidance
- Do not use Sahi logging guidance for new Scenario Editor tests.
- Retain old logging details only when maintaining a legacy test that cannot yet be migrated.
- Use current AIQ output and Test Node logs for supported troubleshooting.
- Mark legacy Sahi dependencies for migration or removal.
Validation workflow
- Identify whether the failing asset still depends on Sahi.
- Collect current AIQ execution output first.
- Use legacy Sahi notes only if required to support the old asset.
- Document the migration path to supported Scenario Editor behavior.
Last updated: September 20, 2026