Troubleshoot an integration
Start with a small read request in the intended project, then add the rest of the workflow.
| Symptom | What to check |
|---|---|
401 or a token error |
Token value, environment variable name, revocation and API region |
A known record returns 404 |
Project ID, resource ID and US/EU host |
A write returns 403 |
Token owner’s project membership and operation permission |
| A collection looks incomplete | Pagination and filters; do not assume the first page contains everything |
| SDK drops a property you supplied | SDK property names and installed package version |
| A plan has no cases immediately after bulk-add | Wait for the cases to appear before assignment or execution |
| A result updates the wrong run | Execution ID, run ID and configuration, not just repository case ID |
| BDD case edits fail | Change the feature file and sync it instead |
| MCP cannot start | Node version, TC_API_TOKEN, API URL and the client/server configuration |
Check versions
Section titled “Check versions”npm list @testcollab/sdktc --versiontc report --helpFor MCP, check the package version configured in your client and restart the server after configuration changes.
Ask for help
Section titled “Ask for help”Contact support@testcollab.com with the client/package version, request method, status code, region and a minimal sanitized example. Remove tokens, token-bearing URLs and customer data from logs before sharing them.