Security Agent sourceCode hits INTERNAL_ERROR in Tokyo but works fine in us-east-1
1 min read
Ran a Security Agent pentest with assets.sourceCode pointing to a ZIP file on S3 in the Tokyo region (ap-northeast-1). Setup Testing Environment failed with INTERNAL_ERROR. Tried twice, same result both times.
Isolation steps:
- S3 Source Access Validation passed (file retrieval was fine)
- Removing
sourceCodefrom the same environment → test completed normally - Using
documentswith the same file → test completed normally
Tried the exact same sourceCode configuration in us-east-1 — no INTERNAL_ERROR, completed successfully through all four phases. When sourceCode is used, CODE SCANNER [BUSINESS LOGIC / IMPORTANT FLOWS / FRAMEWORKS] runs during STATIC_ANALYSIS, and this processing may be unstable in the Tokyo region as of April 2026.
If you need sourceCode in Tokyo, consider documents as a fallback. documents still improved detection by 2.6x over URL-only in our testing.
