RPC nested mappable parameters no longer refresh with updated server data

Hi Make.com team,

We are the developers of CraftMyPDF.

In our Make app, we use RPC to dynamically generate nested mappable fields when users refresh the module. This used to work correctly. Each time the user refreshed the module, Make would call our RPC endpoint and display the latest fields returned from our server.

However, recently some users reported that refreshing the module always returns the same fields, even after the data has changed on our server.

For example, we use a nested RPC like this:

===

“nested”: “rpc://createMappableParameters?template_id={{parameters.template_id}}&version={{parameters.version}}”

===

Previously, when we hit the refresh button of the module, the nested mappable parameters would update after refreshing the module.

Now, the fields appear to be cached or not refreshed properly, and users keep seeing the old fields.

Could you help us check if there has been any recent change to how RPC-based nested mappable parameters are refreshed or cached?

Thanks!

Hi @craftmypdf, :wave:

The Make Community is other users such as yourself, who won’t have insight into this kind of internal info. Would you mind please opening a ticket with Customer Care? They should be able to help you through this.

Marina :make:

Hi Marina,

Thanks for getting back to me.

However, the account for this app is currently on a free plan, and I can’t find a way to contact customer support from that account. Is there another way to reach customer support for this?

P/S: We do have another account on a paid plan, but that account is used for other automations.

Cheers,
Jacky

Hey there @craftmypdf :waving_hand:

Unfortunately, after the 3-month initial period, users on the Free plan cannot access our Customer Care team.

Thanks for understanding :folded_hands:

I see you were able to create a ticket with your paid account; great to see that!

Cheers :smiley:

Hi Vendy, yeah I did and thanks for checking!