Troubleshooting
Troubleshooting Playwright integration with Currents
If you are experiencing issues with using @currents/playwright, enable debug mode to collect more information about the failure and submit a support request via our support channels.
TL;DR share the following information
Collect environment information
Package Versions
Currents Run ID or Dashboard URL associated with the issue
Screenshots or video recordings if applicable
Full error message, including the stack trace, if available
Full and relevant CI execution logs with sensitive information redacted
CI pipeline configuration
The exact commands used during the execution
Relevant configuration of the CI setup stages
Collect and share the debug logs
npx pwc --pwc-debug=full ...ORnpx pwc-p --pwc-debug=remote ...ORDEBUG=currents* playwright test ...
1. Collecting Environment Information
Please collect the following information to help us effectively debug the problem:
The associated dashboard Run URL
Screenshots if applicable
Your setup method and configuration files
The exact command used to run playwright
Environment information (use the command below)
Use the following command to print information about your CI environment
2. Activate Debug Mode
Capture and share the full debug log - that will help the support person identify the root cause faster
@currents/playwright simplifies collecting the debug information by automatically uploading the logs to Currents.
To enable uploading the debug logs:
For
pwccommand-line executable runpwc --pwc-debug=fullORFor
pwc-prunpwc-p --pwc-debug=fullORSet environment variable
DEBUG=currents* playwright test...
--pwc-debug enables uploading the debug logs to our servers (see pwc-p run documentation):
remoteuploads the debug logs to Currents servers;fullprints the logs to stdout and also upload them to Currents.
For example:
When enabled, the debug logs will be uploaded to Currents servers and a confirmation message will be shown after the run's completion, for example:

CI Link Issues
Problem: CI link is missing or incorrect in the dashboard
Currents displays a link to the CI job/run where the tests were executed. If this link is missing or incorrect:
Possible causes:
Auto-detection failed — Your CI provider environment variables are not available in the test environment (e.g., inside a Docker container, custom runner, or self-hosted CI)
Custom CI system — Your CI provider is not automatically recognized by Currents
URL override needed — You need to manually specify the CI URL
Solution:
Set the CURRENTS_CI_URL environment variable to provide the correct CI job/run URL:
For more details on CURRENTS_CI_URL, see Configuration.
Last updated
Was this helpful?