Skip to content

Issue: Zephyr reporter fails with 401 after updating API token (Invalid JWT – 0 parts) #219

Description

@Baskar5532

Description

After updating to a new Zephyr API token, the Playwright Zephyr reporter fails to upload test results and returns a 401 Unauthorized error.
This happens even when the token is freshly generated and correctly configured.

Error Output
[zephyr reporter]: Failed to upload results. Error:
Status: 401
Headers: Object [AxiosHeaders] {
date: 'Wed, 21 Jan 2026 07:04:25 GMT',
'content-type': 'application/json',
'content-length': '63',
connection: 'keep-alive',
'strict-transport-security': 'max-age=31536000; includeSubDomains'
}
Data: { error: 'The token was expected to have 3 parts, but got 0.' }

Questions

Has the Zephyr API token format changed recently?

Is playwright-zephyr@1.1.0 compatible with the latest Zephyr Scale JWT format?

Are there additional headers or configuration required for new tokens?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions