Custom App: Scenario Still Shows Old Module Schema After Update

:bullseye: What is your goal?

To see the scenario module reflect the latest updates to the “Array of mappable parameters” configuration.

:thinking: What is the problem & what have you tried?

I added a new module “Find Email” to an existing custom app and used the existing connection.
However, when I create a scenario and select this module:

  • The connection field is not shown in the module configuration form

  • The module still shows the old input structure (old Array of mappable parameters)

  • The latest updates to the module schema are not reflected in the scenario UI

Because of this, I’m unable to configure the module correctly in the scenario.

  • Updated the Array of mappable parameters in the module definition

  • Saved all changes and verified the app version

  • Tried creating a new scenario

  • Checked in Incognito mode and refreshed the page

  • Verified that the module is using an existing connection

  • Confirmed the app is private and published

Despite this, the scenario still shows the old module configuration and does not display the connection field.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Hello Make Team,

I am working on an existing published custom app. I recently added a new module called “Find Email”, and this module uses the existing connection defined in the app.

However, when I create a new scenario and select the Find Email module, I face the following issues:

  1. The connection field is not shown in the module configuration form (even though the module uses an existing connection).

  2. The form only shows a single input field named user-id, which appears to be from an older “Array of mappable parameters” configuration.

  3. I have already updated the module mapping and inputs, saved the app, and published the changes, but the scenario UI still shows the old configuration.

Could you please help confirm:

  • Whether scenarios cache module schemas after creation

  • If a new app version or reinstall is required for updated module inputs and connection fields to appear

  • Or if there is any additional step required when updating modules in an existing published custom app

Thank you for your help.

You’ll have to refresh the page to load the updated module fields.

Not if you are testing your own private app or using another private app.

A review and publish is required if you want to push changes to external users as a public app.

@samliew

Thanks for the clarification.

Just to add more context from our side:

Our app new version is not yet published.

We need to test the app internally within our organization first, and only after that we plan to submit it for review and publishing.

Currently, we are not able to properly test because while creating a scenario, the module form is not loading correctly (connection is not shown, and only an old “Array of mappable parameters” field appears, even after updating it).

Because of this, we are concerned that publishing without validating the changes internally may result in issues or break existing functionality.

Could you please let us know how we can test the latest changes in a private app scenario before submitting it for review?

Problem Description

I added a new module “Find Email” to an existing custom app and used the existing connection.
However, when I create a scenario and select this module:

The connection field is not shown in the module configuration form

The module still shows the old input structure (old Array of mappable parameters)

The latest updates to the module schema are not reflected in the scenario UI,

please refer the attachments

Additional Observations / Doubts

  • This issue occurs only in one Make account

    • I tested the same app setup in another Make account, and it works correctly there
  • In the affected account, we recently had an **App Ownership Transfer

    **
    Could the Make team please check if there is any account-level issue affecting this app or scenario builder

Following up on the issue raised earlier.

This issue occurs only in Clearout Make account

  • I tested the same app setup in another personal Make account ( Manick ), and it works correctly there

  • In the Clearout Make account, we recently had an App Ownership Transfer

    Could the Make team please check if there is any account-level issue affecting this app or scenario builder

This is currently blocking our progress, so I’d appreciate it if you could look into it and share an update.

@DavidGurr_Make David, is this something you can check internally or have someone reach out to Clearout?

Thanks @Henk-Operative

I’ve escalated this to our team that handles App Ownership Transfers - someone will reach out to the email address supplied in the ownership transfer.

2 Likes