BrowserStack Automate API startTime precision missing when using personal access tokens

Issue Overview

The Session Status endpoint of BrowserStack Automate API returns a startTime field that should contain the exact timestamp of when a session began. When authenticating with a personal access token, the field is often omitted or rounded to the nearest minute, lacking millisecond precision.

Unresolved Decision

It is unclear whether this behavior is intentional—perhaps a backward‑compatibility fallback—or an undocumented regression affecting newer authentication mechanisms.

Key Constraints

• Behavior appears consistently across multiple API versions but may vary with session age.
• Documentation states startTime is optional and may be omitted for older sessions, but no explicit cutoff is provided.
• Personal access tokens are a relatively new authentication method; legacy support may be incomplete.

Questions for Investigation

1. Is the omission or rounding of startTime an intentional design choice for sessions authenticated via personal access tokens?
2. If intentional, what is the documented threshold (e.g., session age or API version) that triggers this behavior?
3. Can the precision of startTime be restored by modifying request parameters or using alternate authentication credentials?