Troubleshooting Guide¶

401 Unauthorized: Token or session expired
403 Forbidden: Permission denied
404 Not Found: Resource doesn't exist
500 Internal Server Error: Server-side issue

Verify:
- Email address is correct
- Password is typed correctly
- Caps Lock is not enabled
- Browser is not auto-filling wrong credentials

Clear:
- Cookies for the data-conductor domain
- Local storage
- Session storage
- Browser cache

Verify:
- Your IP is in the trusted IP list
- VPN/proxy isn't changing your IP
- Network firewall allows access
- Organization hasn't restricted access

Review:
- Organization session timeout settings
- Browser security settings
- Third-party cookie blocking
- Browser extensions interfering

Check:
- Stable internet connection
- Corporate proxy settings
- Firewall rules
- DNS resolution

# Test basic connectivity (if you have command line access)
telnet your-database-host 5432  # PostgreSQL
telnet your-database-host 3306  # MySQL
ping your-database-host

-- Test with a simple SQL client first
SELECT 1 as test;

Check:
- Database server firewall rules
- Cloud provider security groups
- VPC/network configuration
- SSL/TLS requirements

-- Add EXPLAIN to understand query execution
EXPLAIN (ANALYZE, BUFFERS)
SELECT customer_id, COUNT(*)
FROM orders
WHERE order_date >= '{{START_DATE}}'
GROUP BY customer_id;

-- Create indexes on frequently filtered columns
CREATE INDEX idx_orders_date ON orders(order_date);
CREATE INDEX idx_orders_customer ON orders(customer_id);
CREATE INDEX idx_orders_date_customer ON orders(order_date, customer_id);

-- Before: Inefficient query
SELECT * FROM large_table WHERE DATE(created_at) = '2024-01-01';

-- After: Index-friendly query
SELECT * FROM large_table
WHERE created_at >= '2024-01-01'
  AND created_at < '2024-01-02';

-- Check for common syntax issues:
- Missing quotes around string variables
- Incorrect variable names
- Database-specific SQL syntax
- Reserved keywords used as column names

Verify:
- Variable names match exactly (case-sensitive)
- Test values are provided
- Variable types are correct
- No special characters causing issues

-- Database user needs proper permissions:
GRANT SELECT ON schema.table_name TO data-conductor_user;
GRANT EXECUTE ON schema.function_name TO data-conductor_user;

Check:
- Variable name spelling
- Variable is defined in Variables panel
- Test value is provided
- Variable type is appropriate

-- Correct variable usage:
WHERE region = '{{REGION}}'        -- String variable
WHERE amount > {{MIN_AMOUNT}}      -- Number variable
WHERE active = {{IS_ACTIVE}}       -- Boolean variable

-- Incorrect usage:
WHERE region = {{REGION}}          -- Missing quotes for string
WHERE amount > '{{MIN_AMOUNT}}'    -- Quotes around number

Steps:
1. Switch to Preview tab
2. Verify variables are replaced
3. Check SQL syntax is correct
4. Test with simple values first

# Test your CRON expression:
# Use online tools like crontab.guru
0 9 * * *        # Daily at 9 AM - VALID
0 9 * * MON-FRI  # Weekdays at 9 AM - VALID
0 25 * * *       # Invalid hour (25) - INVALID

Check:
- Organization timezone setting
- Server timezone vs. expected timezone
- Daylight saving time effects
- CRON expression interpretation

Monitor:
- System CPU and memory usage
- Database connection pool status
- Concurrent execution limits
- Queue backlog

# Test API endpoint manually
curl -X POST \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"variable1": "value1"}' \
  https://your-instance.com/api/execute/deployment-id

Verify:
- Token is active and not expired
- Token has required permissions
- Authorization header format is correct
- Token is for the correct organization

// Correct payload format:
{
  "variables": {
    "START_DATE": "2024-01-01",
    "REGION": "US-West",
    "LIMIT": 100
  }
}

Actions:
- Clear browser cache and cookies
- Disable unnecessary browser extensions
- Update browser to latest version
- Try incognito/private mode

Check:
- Internet connection speed
- Corporate proxy/firewall settings
- VPN performance impact
- DNS resolution speed

Optimize:
- Add LIMIT clauses to large queries
- Use pagination for result sets
- Filter data more aggressively
- Consider pre-aggregated views

-- Monitor long-running queries
SELECT query, query_start, state, wait_event
FROM pg_stat_activity
WHERE state = 'active'
AND query_start < NOW() - INTERVAL '5 minutes';

Monitor:
- CPU usage during query execution
- Memory consumption patterns
- Database connection count
- Disk I/O patterns

-- Check source data quality
SELECT
    COUNT(*) as total_rows,
    COUNT(DISTINCT customer_id) as unique_customers,
    MIN(order_date) as earliest_date,
    MAX(order_date) as latest_date,
    COUNT(CASE WHEN total_amount IS NULL THEN 1 END) as null_amounts
FROM orders
WHERE order_date >= '{{START_DATE}}';

-- Test filters step by step
SELECT COUNT(*) FROM orders;  -- Total count
SELECT COUNT(*) FROM orders WHERE order_date >= '{{START_DATE}}';  -- Date filter
SELECT COUNT(*) FROM orders WHERE order_date >= '{{START_DATE}}' AND region = '{{REGION}}';  -- Combined filters

-- Check for data loss in joins
SELECT
    o.customer_id,
    COUNT(o.*) as order_count,
    CASE WHEN c.customer_id IS NULL THEN 'Missing Customer' ELSE 'Found' END as customer_status
FROM orders o
LEFT JOIN customers c ON o.customer_id = c.customer_id
GROUP BY o.customer_id, c.customer_id;

Check:
- User role (Admin, User, Viewer)
- Organization membership
- Feature-specific permissions
- Recent permission changes

Verify:
- Current IP is in trusted list
- CIDR ranges are correct
- VPN/proxy IP changes
- Recent IP list modifications

Confirm:
- User owns the resource
- Resource is shared appropriately
- Organization-level permissions
- Workspace access rights

# Check your current IP
curl ifconfig.me
# Or visit whatismyipaddress.com

Check:
- NAT/proxy changing your IP
- Dynamic IP assignment
- VPN endpoint changes
- Corporate firewall rules

Examples:
192.168.1.100/32  - Single IP
192.168.1.0/24    - Range 192.168.1.1-254
10.0.0.0/8        - Large corporate range

42601: Syntax error
42703: Column doesn't exist
42P01: Relation doesn't exist
53300: Too many connections

1064: SQL syntax error
1146: Table doesn't exist
1054: Unknown column
1040: Too many connections