Troubleshoot VB-OS Connector Failures
Connection Test Failures
Section titled “Connection Test Failures”Invalid Credentials
Section titled “Invalid Credentials”The connector cannot authenticate with the provider.
Fix:
- Verify credentials are correct
- Check that the provider account is active
- For OAuth connectors, re-authorize if the token has expired
Network Errors
Section titled “Network Errors”The connector cannot reach the provider endpoint.
Fix:
- Verify the provider URL is correct
- Check network connectivity and firewall rules
Evidence Mapping Errors
Section titled “Evidence Mapping Errors”Categorical Map Fail-Closed
Section titled “Categorical Map Fail-Closed”A categorical_map transform received a value that does not match any key in the mapping.
Fix:
- Add the missing value to the mapping configuration
- This is by design: unmapped values fail closed to prevent unknown data from passing through
Source Path Not Found
Section titled “Source Path Not Found”The source_path does not resolve to a value in the provider response.
Fix:
- Verify the dot-notation path matches the provider’s response structure
- Use the connector’s resource/schema discovery endpoints to inspect available fields
Webhook Verification Failures
Section titled “Webhook Verification Failures”Invalid Signature
Section titled “Invalid Signature”The inbound webhook payload failed signature verification.
Causes:
- Webhook secret mismatch between the provider and VB-OS
- Payload was modified in transit
- Wrong signature method configured
Fix:
- Verify the webhook secret matches the provider’s configuration
- Check that the correct signature method is selected (Stripe, GitHub HMAC, or platform HMAC)
Next Steps
Section titled “Next Steps”- Connectors Overview: how connectors work
- Evidence Mapping: mapping reference
- Authentication Patterns: connector auth
