I encountered an issue where variables set in the Tools (Get multiple variables) module, taken from Telegram Bot Watch Updates, are not passed to the next module (e.g., Supabase Create a Row). In the scenario, all settings and mappings were correct, and the logs for both Watch Updates and Tools showed the expected values. However, the next module (Supabase) received only null or empty values for all fields.
Possible causes:
Internal Make bug causing data “sticking” or cache issues between modules, even when configuration is correct.
Re-linking variables or refreshing the mapping does not help.
Deleting/re-adding variables and modules sometimes temporarily resolves the issue.
What I tried:
Double-checked variable mappings and filters (all correct).
Verified data presence in all previous modules.
Deleted and recreated the Tools and Supabase modules from scratch, which resolved the problem.
Is this a known Make.com bug?
Are there best practices to avoid this issue or force a refresh of module variable links?
Any technical insight on what triggers this data transfer failure?
I need help! Thanks.
Thank you, I’ll try it a little later and write back!