• TROUBLESHOOTING AND FAQS • SETUP GUIDE

Why Didn’t an Integration Receive a Submission or Approval?

By Rivio Support Team
2 min read

What you will achieve in this guide

Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.

EXPECTED SETUP TIME 5-10 Minutes
COMPATIBILITY All Shopify Themes & Plans
TECHNICAL DIFFICULTY Zero Code Required

Check integration configuration, required applicant data, spam status, and errors when an application event does not arrive.

Before you begin

Record the affected store, form name, slug, application reference if available, and approximate time. Reproduce the issue once with dummy data and note the exact message before changing settings.

Trace the application to the destination

Confirm the application and decision first, then inspect connection state, the destination identifier, and required email data. Spam is excluded and email-marketing sync is skipped when no applicant email exists.

Manual, API, and automatic approval events are supported in the current release. Do not repeatedly change a status merely to trigger another event; inspect the error and correct the connection, then use a controlled fresh test.

Reference and examples

Check Action
Application/status Confirm the original non-spam record and decision.
Email missing Add applicant email for email-marketing workflows.
Wrong destination Review list/audience/group/channel/sheet tab/endpoint.
Authorization Reconnect or correct the intended connection.
Google sync Review old-scope banner, file link, tab, and logged error.
Still failing Send support reference, event path, destination, and time without credentials.

Diagnose and resolve the problem

  1. Confirm the submission and final decision in the app.

  2. Check the connected account and destination list, channel, sheet, or URL.

  3. Ensure the application contains an email when the marketing integration requires one.

  4. Confirm the application is not Spam.

  5. For Google Sheets, inspect reconnection requirements, selected tab, and logged sync errors.

  6. Run a controlled fresh test and check the external destination before retrying an approval.

Example

Approve a fresh non-spam application manually and look for its known email or reference in a connected test destination.

Expected result

The supported approval path sends its event once; account, destination, and errors are checked if it is missing.

Limits and important behavior

  • Current approval events include manual admin, API, and automatic approvals.
  • Each approval event is sent once, but external workflows should still guard against accidental duplicate processing.
  • Background integration failure does not invalidate the received submission.

If you still need help

If the checks do not resolve the issue, contact support@rivioapps.com with the affected form or application reference, time, exact error, and what you already tested. Mask private applicant data and never include API keys or SMTP passwords.

Screenshots to add

Screenshot placeholder: Capture the relevant app screen for “Why Didn’t an Integration Receive a Submission or Approval?” after completing the setup. Show the controls used to confirm the submission and final decision in the app. Add a second screenshot showing the result of this check: Run a controlled fresh test and check the external destination before retrying an approval. Use dummy applicant details and mask any secrets.

Related guides

If these checks do not resolve the issue, contact RivioApps Support with the form name, application reference where relevant, error, and time. Do not include passwords or access keys.