What is your goal?Copying filters without deleting attached notes.
What is the problem & what have you tried?Everytime I use “Copy Filter” in Make DevTool, it erases ALL scenario notes
Error messages or input/output bundlesNotes erased.
Share a link to your scenario
Screenshots (scenario flow, module settings, errors)This is a DevTool bug, not user error. The “Copy Filter” function is wiping scenario-level notes as a side effect of the copy operation.
Next time, before you use “Copy Filter,” take a screenshot of your notes or paste them into a notepad. After the copy, paste them back in.
In the meantime, don’t rely on Copy Filter for critical scenarios. If you need to duplicate filters, do it manually and select the filter logic, take screenshots, and recreate it on the destination module. Takes a minute and keeps your notes safe.
This is a known issue, so Make probably knows about it.
Thanks for the insight @Karmic , but Make needs to look into fixing this as no one has time to manually copy complex AND / OR filters. Sure this is the only solution for now, completely understand.
Anyone else ran into this issue besides when copying filters? Does it happen with other DevTool functions?
Yes, totally get you on that. Rebuilding complex AND / OR filters by hand is a hassle, especially once you start nesting them. For now we are stuck with this workaround, but I agree it really should be a prioritized feature and something Make puts on the roadmap.
Welcome to the Make community!
This is a confirmed bug with the Make DevTool, as the MDT was created way before the “Notes” feature was introduced, and has not been updated yet. Please report it to customer support.
For now, please do NOT use the Make DevTool to copy filters. I have posted the “correct” way of copying filters in the next post below.
As this is a community (peer-led) forum, we can only help with using the Make platform as intended (scenario building, troubleshooting scenario/module error messages, etc.). We cannot assist with platform/technical issues like these.
For account, billing, or technical issues, contacting Make support by creating a ticket is the only official option available to Make customers.
Make support has access to your specific account details, scenario, execution history, server-side logs, and has internal tools to investigate the issue further. If the issue is with a custom app, Make support will be able to reach out to the external team responsible for maintaining it. Also, you might need to share potentially sensitive information about your account, organisation, scenario, and execution history logs, which is not advisable here on this public forum.
Before creating a support ticket, do try to look around if others are facing the same problem, and if there are further steps you can take. Here are some things you can do —
Check the Make Status page to see if it is an ongoing network-wide issue/outage and view any updates (example).
Search this Make forum to see if there are any discussions, updates, and workarounds. Here are some possible search terms you can use:
tags:error bug "not working"
If you are logged-in, you can head to the new ticket page to submit a ticket. (If you are unable to login to your main account, it is advisable to create an account to access this page.)
Above: Screenshot of the Contact Support page
After submitting your support ticket, you should receive a confirmation email with the subject “Ticket Created” together with a summary of what you submitted. If you do not receive this automated reply within minutes, try creating a ticket again. Example of email subject: [#1234567] Ticket created | Technical challenge
If you do not receive a response from Make support, simply be patient. Make support receives thousands of tickets daily, hence tickets have to be prioritised based on the severity of the incidents and organisation’s plan. For more information about the different levels of customer support for each plan, refer to the “Support” section on the Pricing page, or on your organisation’s Subscription pag. If you are a free customer, you can create a Pro account to get quicker support via the ticketing system.
When your issue is resolved one way or another, we’d love to hear more details about the cause, and how you managed to solve it (including use of workarounds). By sharing your findings and solutions, we are contributing to this knowledgebase to enable others to search for answers to similar problems.
— @samliew
The recommended way to copy a filter, is to copy the module that the filter is attached to.
Right-click the module you want to copy, select “Copy module”.
Right-click on an empty space in your scenario, and select “Paste”.
Above: Screen recording demonstrating the pasted module with duplicated filter
Connect the module to where you want the copied filter to be!
 |
Main difference between Clone and Copy: |  |
|---|---|---|
| Selecting “Clone” will only make a copy of the module, without the filter! |
Hope this helps! If you are still having trouble, please provide more details.
— @samliew
