Solving Multiple Scenario Runs in Monday.com Automation

Problem

One of our users was trying to automate a process on Monday.com where they wanted to count the number of files in a file column immediately after upload, extract the name of the uploader, and rename the files using information from other columns. However, they were facing a problem where the scenario was running as many times as there were files, despite using an aggregator. They also didn't know how to add an incrementing number to the file name for individuality.

Solution

After some discussion in the community, a solution was suggested to use a different trigger for the scenario. Instead of triggering the scenario with each file upload, it was suggested to use a button column as a trigger. After the files are uploaded, the user can simply click on this button to trigger the scenario. This prevents the scenario from running multiple times with each file upload.

The user tested this solution by changing the trigger to a status column change to a defined status ('Uploaded'). This worked perfectly and the scenario ran only once. They were also able to rename the files to have individual names by using the aggregator to add the bundle order position to the bundles. This allowed them to use the order position in the final module to add it to the name just before the file extension.

Troubleshooting Tips

If you're facing a similar problem, consider the following tips:

  • Check your triggers: Make sure your scenario isn't being triggered multiple times unnecessarily.
  • Use an aggregator: If you're dealing with multiple files or data points, an aggregator can help bundle them together and prevent multiple runs of the scenario.
  • Consider using a different trigger: If your current trigger is causing issues, consider using a different one. In this case, a button column or a status column change was used as a trigger.

Conclusion

Automation can be a powerful tool to streamline your workflows, but it can sometimes be tricky to get it right. In this case, a simple change in the trigger for the scenario solved the problem. Remember, the community is always here to help if you're stuck!

You do have further questions?

Ask your question via E-Mail: Richard@make-app.de
Book a paid Support & Consulting Session
New Make.com user? Sign up through this Affiliate Link to receive 10.000 operations for FREE.