ATP360 Known and Fixed Issues
No platform is ever perfect—especially at the cutting edge—and ATP360 is no exception. This page is your transparent view into where things aren’t quite there yet, alongside what’s been fixed along the way.
What's new
Can be found in the ATP360 change log Changelog | ATP360
9th June 2026 - 1.1.0
Fixed Issues
-
Parsing method can be changed mid-run (27574)
- Incorrect step count in test results (27586)
Known Issues
1. Environment provisioning fails due to Azure policy restrictions (27877)
Issue: Deployment of ATP360 resources can fail due to Azure Policy violations, specifically requiring storage accounts and Key Vaults to disable public network access and enforce firewall protections.
Impact: Environment creation fails entirely, blocking users from deploying or using ATP360 until policy requirements are met.
Workaround: Ensure all required Azure resources comply with organisational policies before deployment — specifically disable public network access on storage accounts and configure Key Vault firewall settings in line with policy requirements.
2. Action Log entries lost after Orchestrator restart during Live Run (27703)
Issue: Assistant entries in the Action Log are lost during the Pause and Recover process if the Orchestrator restarts mid-run.
Impact: Loss of execution history reduces visibility into test progress and makes troubleshooting more difficult, especially across interrupted runs.
Workaround: Avoid restarting the Orchestrator during active runs where possible. If a restart occurs, rely on external logs or rerun the test to capture a complete Action Log.
2. Incorrect error when AI agents are out of credit (27529)
Issue: The wrong error message is displayed when AI agent credits are exhausted.
Impact: Misleading errors can delay troubleshooting and obscure the root cause of failed test runs.
Workaround: Check available credits with your AI provider and replenish as needed before rerunning tests.
19th May 2026 - 1.0.0 Private Preview Phase 1
Fixed Issues
This is the first version of ATP360 - none in this release.
Known Issues
1. Incorrect error when AI agents are out of credit (27529)
Issue: The wrong error message is displayed when AI agent credits are exhausted.
Impact: Misleading errors can delay troubleshooting and obscure the root cause of failed test runs.
Workaround: Check available credits with your AI provider and replenish as needed before rerunning tests.
2. Parsing method can be changed mid-run (27574)
Issue: Users can switch parsing methods while a parse is in progress.
Impact: This can result in inconsistent outputs, UI inconsistencies, or partial/invalid results.
Workaround: Avoid changing parsing methods during execution. Cancel and restart the process if needed.
3. Incorrect step count in test results (27586)
Issue: The number of steps shown in test results is not mapped correctly.
Impact: Reported step counts may not reflect actual execution, reducing confidence in summaries and reporting.
Workaround: Use detailed step-level views as the source of truth until resolved