1. Form Submission Errors
- Check required fields and correct data format (especially email and URLs).
- Ensure at least one package is selected for marketplace submissions.
- For applications, provide a resume URL or upload a resume file.
2. Missing Confirmation Emails
If a submission succeeds but a user does not receive email, verify SMTP credentials and inbox spam filtering first.
Admin notifications and client confirmations are sent separately, so one can succeed while the other fails.
Checklist
- - SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASS are set
- - SMTP_FROM uses a verified sender address
- - Target inbox allows external SMTP messages
- - Application logs are checked for email send errors
3. Resume Upload Problems
- Allowed file formats: PDF, DOC, DOCX.
- Maximum file size: 5MB.
- If MIME type is missing, file extension is used as fallback validation.
4. API Response Codes
Common status meanings
200: Success
400: Validation error (input is missing or invalid)
500: Server error during processing
503: Email service unavailable or temporarily misconfigured5. When to Escalate to Support
Escalate when issues persist after validation, especially for email delivery failures, repeated 500 errors, or inconsistent data persistence.
Checklist
- - Capture exact timestamp and endpoint
- - Record request payload shape (without sensitive secrets)
- - Include returned status code and message
- - Share expected outcome versus actual behavior
Frequently Asked Questions
A user got a success message but no email arrived. What should we check first?
Check server logs for confirmation email send status and verify SMTP credentials and sender domain reputation.
Can we retry failed submissions safely?
Yes. Most submission flows are designed for retry. Keep a client-side idempotency strategy if your workflow requires strict duplicate protection.