Intake troubleshooting
Review required
Section titled “Review required”This is a safe outcome, not a failed request. Open the event, correct the extracted details, select a service if known, and approve the CRM creation.
Duplicate
Section titled “Duplicate”Qonvera has already processed the external event ID. Open the original event instead of changing the ID and submitting the same enquiry again.
503 intake unavailable
Section titled “503 intake unavailable”Verify the dedicated intake service is healthy, the edge-to-origin authentication is correct, the source credential is active under the current pepper version, and the public intake flag is enabled only on the dedicated intake service. Keep the main application’s public intake route disabled when using the dedicated boundary.
Email extracted the sender instead of the lead
Section titled “Email extracted the sender instead of the lead”Notification emails often come from a fixed sender such as noreply@.... The actual lead may be inside the subject, text, or HTML body. Review the extracted fields before approval. For reliable automation, have the source emit structured labels and a correlation ID.
Retry safely
Section titled “Retry safely”Use the Intake event’s replay action only for eligible failed or review states. Replays are bounded and idempotent. Confirm the attempt timeline and CRM links before retrying again.