Troubleshooting
This guide will help you resolve the most common problems with Zuora Workflow Manager.Installation problems
Error: “Cannot connect to database”
Symptom:- Lando is not started
- Database container is not ready
- Incorrect database credentials
Error: “Permission denied”
Symptom:Error: “Port already in use”
Symptom:Synchronization problems
Workflows not synchronized
Symptom: Click “Sync Workflows” but no workflows appear Diagnosis:- Verify Client ID and Secret
- Verify correct Base URL
- Test credentials with Postman
Error: “Invalid Zuora credentials”
Symptom:- Incorrect Client ID
- Incorrect Client Secret
- Expired credentials
- Incorrect Base URL
Slow synchronization
Symptom: Synchronization takes a long time Possible causes:- Many workflows to synchronize
- Zuora network latency
- Slow database
- Single worker
Queue problems
Jobs stuck in queue
Symptom: Jobs in “Jobs Waiting” but not being processed Cause: Queue worker not active Solution:Jobs fail repeatedly
Symptom: Same job fails 3 times Diagnosis:Queue connection refused
Symptom:Cache problems
Cache not updating
Symptom: Changes not visible in application Solution:Error: “Cache connection refused”
Symptom:Authentication problems
Cannot login
Symptom: Correct credentials but login fails Diagnosis:Google OAuth not working
Symptom: Error during Google login Diagnosis:-
Verify Google credentials:
- Google Cloud Console → Credentials
- Verify Client ID and Secret
- Verify Redirect URI:
{APP_URL}/oauth/google/callback
-
Verify Settings:
- Settings → General Settings → OAuth Configuration
- OAuth Enabled = true
- Correct Client ID and Secret
-
Verify allowed domains:
- Settings → OAuth Allowed Domains
- Add email domain (e.g.,
example.com)
Performance problems
Slow application
Diagnosis:Slow database
Diagnosis:Deployment problems
Error 500 in production
Diagnosis:Queue worker not starting in production
Diagnosis:Useful debugging commands
Check system status
Log monitoring
Database debugging
Cache debugging
Getting support
If the problem persists:1. Gather information
2. Open an Issue
Go to GitHub Issues and include:- Problem description
- Steps to reproduce
- Output from commands above
- Application version
- Environment (development/production)