41.1 Troubleshooting AIUNIFY Funnels

This chapter covers common user-level issues that can occur while creating, configuring, publishing, and operating Landing Pages in AIUNIFY Funnels.

The troubleshooting guidance is organized around the actual user workflows documented throughout this manual: Landing Pages, Builder, Domains, Forms, Leads, mailing integrations, Products, Payments, and Orders.

When troubleshooting, first identify the exact part of the workflow that failed. A problem with the Builder, for example, should not immediately be treated as a payment or domain problem.

41.2 Use the Exact Error Message

AIUNIFY Funnels returns specific messages for many common failures. Record the exact wording before changing multiple settings.

Useful information to preserve during troubleshooting includes:

1. The exact error message.
2. The Landing Page Name.
3. The action you were performing.
4. Whether you were working in Builder, Settings, Leads, Products, or Orders.
5. Whether the issue occurs in the authenticated workspace or on the public Landing Page.

41.3 Builder Not Available on a Small Mobile Screen

The current Builder explicitly displays:

Builder not work on mobile

when the editing viewport is too narrow.

This is a Builder limitation rather than evidence that the Landing Page itself cannot be viewed by mobile visitors.

Use a desktop or sufficiently wide browser for Builder editing, then test the actual public Landing Page separately at mobile sizes.

41.4 Builder Changes Do Not Appear to Save

The Builder uses remote storage and saves its page data through the Landing Page Builder update workflow.

If the application reports:

Updated failed

do not continue making a large number of additional edits.

Instead:

1. Remain on the Builder page if possible.
2. Confirm that your authenticated session is still active.
3. Retry the supported Save operation.
4. If the save succeeds, reopen the Landing Page and confirm the changes persisted.
5. If it continues failing, preserve the exact error and the Landing Page involved for support review.

41.5 Template Cannot Be Found

If the selected Template is no longer available to the creation or Preview workflow, AIUNIFY Funnels can return:

Template id not found

Return to Create Landing Page, reload the currently available Template Library, and choose an active Template again.

Do not manually reuse an old or guessed Template identifier.

41.6 No Landing Pages Are Listed

If no Landing Pages are available in the current result, the interface can display:

No Landing Page Found

You don't have any Landing Page.

Confirm that you are signed into the intended user account. If this is a new account, use New Landing Page or Create Landing Page to begin from an available Template.

41.7 Landing Page Does Not Open Publicly

If the Landing Page exists in My Landing Pages but its public address does not produce the expected page, review these items separately:

1. Confirm the Landing Page is in the intended Published state.
2. Confirm the Domain Type.
3. Confirm the Current domain.
4. If using a custom domain, confirm the external DNS records match the values displayed in Landing Page Settings.
5. Open the exact public domain shown by AIUNIFY Funnels.

Publishing status and domain configuration are separate. A valid domain does not automatically mean the Landing Page is published.

41.8 Subdomain Validation Problem

If the submitted subdomain does not contain the domain structure required by the application, AIUNIFY Funnels can return a message beginning with:

Subdomain must have

followed by the required application-domain value.

Return to Domain Settings and enter a domain value that follows the format expected by the deployed application.

41.9 Custom Domain Does Not Resolve

When using Custom your domain, the Landing Page Settings screen displays the DNS record information required for the installation.

Verify the external DNS provider contains the same:

1. TYPE.
2. HOST.
3. VALUE.
4. TTL.

Do not guess a server value. Use the values shown by AIUNIFY Funnels for the current installation.

41.10 Redirect URL Is Rejected

If a form or payment-success redirect is configured with an invalid URL, AIUNIFY Funnels can report:

Redirect URL Not a valid URL

Enter a complete valid URL and save the Landing Page Settings again.

After saving, test the redirect through the actual public form or payment workflow rather than testing the destination in isolation.

41.11 Image Upload Is Rejected

The Landing Page Builder accepts the confirmed image formats JPG, JPEG, PNG, and SVG.

If an unsupported file is submitted, the application can return:

The file must be an jpg,jpeg,png,svg

Convert or replace the image with a supported format before uploading again.

41.12 Image Appears Missing After Asset Cleanup

Removing an uploaded Builder asset can delete the underlying file from the authenticated user's asset storage.

If an image becomes unavailable after asset cleanup, check whether that same physical file was still referenced elsewhere on either the Main Page or Thank You Page.

When replacing an important image, update the page reference first, save and test the page, and remove the old asset only after confirming it is no longer used.

41.13 Form Reports No Fields to Submit

If the form does not provide usable named fields, AIUNIFY Funnels can return:

Not found any fields submit. You need config name for fields in builder

Open the Main Page Builder and review the form fields. Each field that should be captured must have an appropriate field name.

41.14 Form Reports That All Fields Are Empty

If field names exist but no meaningful submitted values are present, the application can return:

Not found any fields submit. Please enter some fields

Review the form and make sure the fields required by the campaign actually receive values before submission.

41.15 Form Reports Page Not Found

If the submitted Landing Page code cannot be resolved, the form workflow can return:

Not found page id

Verify that the public form belongs to the current Landing Page and that you are testing the current published page rather than an obsolete page or copied fragment.

41.16 Duplicate Lead Email

When an email address has already been captured on the same Landing Page, the duplicate-email workflow can return:

Your Email existed!

When testing repeatedly, use a different recognizable test email address or review the existing Lead record before submitting again.

The confirmed duplicate check is performed for the same Landing Page rather than described as a global account-wide duplicate prohibition.

41.17 Autoresponder Does Not Send

If the Lead is captured but the expected Autoresponder email is not received, review:

1. Confirm the Landing Page form contains a field named email.
2. Confirm the submitted email value is valid.
3. Confirm Message title is configured.
4. Confirm Sender name is configured.
5. Confirm Sender email is valid.
6. Confirm Message text is configured.
7. Confirm any placeholders correspond to actual form field names.
8. Remember that the Autoresponder is processed as a queued job and is separate from the browser redirect.

If the Lead is captured successfully but the Autoresponder repeatedly fails after its Landing Page configuration has been verified, preserve the test Lead details and exact behavior for support review.

41.18 Mailchimp Connection Problem

If Mailchimp does not accept the supplied credential, the integration can report:

Please Enter a valid API key

Verify the API Key belongs to the Mailchimp account being connected, then use the integration connection test again.

41.19 Mailing Integration Connects but Lead Does Not Appear

For Mailchimp, Acellemail, or Mailwizz, a successful Landing Page Lead capture does not by itself prove the external mailing-list operation succeeded.

Check:

1. The intended integration is selected.
2. The connection test succeeds.
3. The correct Mailing list is selected.
4. The Landing Page contains a valid field named email.
5. The form field names align with the intended external merge fields.
6. The contact is checked directly in the external mailing platform.

41.20 Lead Export Contains No Data

If no records exist for the export scope, AIUNIFY Funnels can return:

Not found any data for export

Confirm that Leads exist for the authenticated account and intended Landing Page export scope.

Also remember that CSV export can be feature-dependent in deployments using the optional SaaS package controls.

41.21 CSV Columns Do Not Match Across Campaigns

CSV columns are generated from the actual field keys found across the exported Lead records.

If one Landing Page uses phone and another uses phone_number, those become separate CSV columns.

For cleaner future exports, standardize important form field names across Landing Pages where practical.

41.22 PayPal Checkout Says Payment Settings Are Missing

If the Landing Page owner does not have the required PayPal account settings, checkout can return:

You need config setting payment PayPal in account setting

Open Account Settings → Payment Settings and confirm the appropriate:

1. Environment.
2. Client ID.
3. Secret.

Make sure Sandbox credentials are used with Sandbox and live credentials are used only when intentionally processing live transactions.

41.23 Stripe Checkout Says Payment Settings Are Missing

If the Landing Page owner does not have the required Stripe settings, checkout can return:

You need config setting payment STRIPE in account setting

Open Payment Settings and verify that the appropriate Publishable key and Secret key are both configured.

Make sure both credentials belong to the same intended Stripe environment.

41.24 Checkout Reports Invalid Payment Type

If a checkout request supplies an unsupported payment value, the application can return:

Not found type payment

If no supported payment-method value is supplied, it can return:

Not found payment method or type

Review the Landing Page's supported checkout component rather than manually altering internal payment values.

41.25 Checkout Cannot Find the Product

If the Product identified by checkout cannot be found, AIUNIFY Funnels can return:

Not found products

Open Products, confirm the Product still exists, then review the Landing Page Builder component that is intended to use that Product.

If a Product has been deleted, update the affected Landing Page before directing customers to it.

41.26 Checkout Cannot Find the Landing Page

If checkout cannot resolve the Landing Page code, AIUNIFY Funnels can return:

Not found LandingPage

Confirm that checkout is being started from the current public Landing Page and not from an obsolete or copied page implementation.

41.27 Order Exists but Shows Not Paid

AIUNIFY Funnels creates an Order before the supported gateway workflow is completed, and every new Order begins with its Paid value set to false.

An Order can therefore exist even when payment has not completed.

For PayPal or Stripe:

1. Check whether the customer actually completed the external gateway process.
2. Verify the transaction in the merchant account when appropriate.
3. Do not mark an Order Paid merely to correct an unsuccessful external transaction.

41.28 COD or Bank Transfer Remains Not Paid

COD and Bank Transfer Orders are created without the external PayPal or Stripe paid-confirmation step in the confirmed checkout branch.

They can therefore remain Not paid until the business independently verifies payment.

Only mark the Order Paid after the money has actually been verified through the appropriate business process.

41.29 OPEN, COMPLETED, and CANCELED Do Not Mean Paid

Order operational status and payment status are independent.

OPEN / COMPLETED / CANCELED	Describe the operational Order state.
Paid / Not paid	Describe the saved payment state.

Do not use COMPLETED as a substitute for confirming payment, and do not use Paid as a substitute for confirming fulfillment.

41.30 Cloned Landing Page Has Unexpected Settings

Clone replicates the existing Landing Page record and then changes certain values, including its Name and generated subdomain, while clearing the custom-domain value.

Because other settings can be copied from the source record, review the clone immediately for:

1. Publish state.
2. Domain Type.
3. Form next action.
4. Autoresponder.
5. Mailing integration.
6. SEO and social information.
7. Payment configuration and Product references.

41.31 Deleting a Landing Page Removes Its Associated Leads

The Landing Page model deletion hook removes the Landing Page's associated FormData records.

Critical reminder: deleting a Landing Page also deletes its associated Landing Page Lead/form-submission records.

Export any Lead information that must be retained before deleting the Landing Page.

41.32 Deleting an Individual Lead Is Different

Deleting a Lead removes the selected Lead/FormData record.

It does not perform the same operation as deleting the entire Landing Page.

Confirm which object you are deleting before approving the confirmation prompt.

41.33 Deleting an Order Is Destructive

The standard Order deletion workflow removes the selected Order record and does not provide a user-facing restore step in that operation.

Preserve transaction information required for business, accounting, or retention purposes before deleting an Order.

41.34 Protect Merchant and Integration Credentials

Payment and mailing integrations can require private credentials such as API keys, API tokens, PayPal secrets, or Stripe secret keys.

Do not place private credentials in:

1. Landing Page copy.
2. Lead form fields.
3. Public Custom Header code.
4. Public Custom Footer code.

Use the authenticated Settings area intended for the integration.

41.35 Test One Change at a Time

When troubleshooting a live campaign, avoid changing the domain, form, Autoresponder, payment settings, Builder design, and custom code simultaneously.

Make one controlled change, save it, and test the affected workflow. This makes it easier to identify which change corrected or created the problem.

41.36 Use Recognizable Test Data

When testing forms or checkout:

1. Use clearly recognizable test names and values.
2. Use an email address you can verify when testing email workflows.
3. Avoid confusing test Leads or Orders with real customer records.
4. Remove unnecessary test records only after confirming they are no longer required.

41.37 Test the Entire Visitor Journey

A Landing Page is not fully tested simply because it looks correct in Builder.

For a lead-generation campaign, test:

1. Public domain.
2. Main Page.
3. Form fields.
4. Form submission.
5. Lead capture.
6. Autoresponder when configured.
7. Mailing integration when configured.
8. Thank You Page or redirect destination.

41.38 Test the Entire Payment Journey

For a selling campaign, test:

1. The Product Name.
2. The Gross Price.
3. The Currency.
4. The Landing Page payment component.
5. The merchant credentials.
6. The supported gateway flow.
7. The payment-success destination.
8. The resulting Order.
9. The Paid or Not paid state.
10. The operational Order status.

41.39 Review Desktop, Tablet, and Mobile

Although Builder editing requires a sufficiently wide screen in the current implementation, the public Landing Page should still be reviewed at the device sizes important to the campaign.

After major content, font, image, form, custom-code, or Product changes, review the live Main Page and Thank You Page again.

41.40 Keep Landing Page Names and Form Fields Consistent

Consistent internal naming makes the system easier to operate.

Use descriptive Landing Page names and consistent field keys for recurring information such as:

1. name
2. email
3. phone
4. company

Consistent field names make mailing integration mapping and CSV exports easier to manage.

41.41 Preserve Data Before Destructive Actions

Before deleting a Landing Page, Lead, Product, or Order, determine whether related information must first be retained.

In particular:

1. Export required Leads before deleting their Landing Page.
2. Preserve required transaction records before deleting Orders.
3. Review active Landing Pages before deleting Products they may use.

41.42 Recommended Troubleshooting Sequence

1. Identify the exact workflow that failed.
2. Record the exact error message.
3. Confirm you are using the intended user account and Landing Page.
4. Review only the Settings relevant to that workflow.
5. Correct one issue at a time.
6. Save the change.
7. Retest through the actual public Landing Page when applicable.
8. Verify the resulting Lead or Order record.
9. Verify external email or payment systems separately when they are part of the workflow.
10. If the issue remains, preserve the exact error, Landing Page, and reproduction steps for support review.

41.43 Final Best-Practice Checklist

Landing Pages	Use clear names, verify publishing and domains separately, and test the actual public URL.
Builder	Edit from a sufficiently wide screen, save deliberately, and verify the public result.
Forms	Use correctly named fields and a valid email field when email-based features are required.
Autoresponder	Complete all required sender/message fields and test delivery with a real controlled submission.
Mailing Integrations	Test the connection, choose the correct list, align form field names, and verify the contact externally.
Leads	Review source and captured information, use consistent field names, and export before destructive cleanup.
Products	Verify Name, Gross Price, and Currency before attaching the Product to a live checkout.
Payments	Use the correct merchant credentials and environment and complete a controlled gateway test.
Orders	Manage operational status separately from payment status and verify money movement independently.
Deletion	Understand what data will be removed and preserve required information first.

Final operating principle: Build deliberately, configure each conversion step separately, test the complete public journey, verify the resulting Lead or Order, and preserve important data before destructive actions.