How to get Incomplete exectution notification?

Hi all, Lately I’ve been running into a new problem more and more often, namely silent errors.

Let me explain in more detail. There are hundreds of scenarios of varying complexity in my organization. Among them, there are both scheduled and webhooks.

When any scenario goes down, I get an email notification of the error and can easily monitor this to restore it as soon as possible. This classic scheme has worked well in practice and I can easily monitor a huge number of scenarios in different organizations using the make.com API, as well as tracking incoming emails from make.

This classic scheme works according to the following logic:
There was an error in a scenario module → It stops → I get an alert → The error is manually fixed → The scenario starts.

However, when using the Incomplete executions + Sequential processing OFF option, this logic starts to work differently and I lose the ability to track errors.

There is an error in the script module → It does NOT stop → I do NOT get an alert → The error is NOT fixed → The script runs with errors → I find Incomplete executions by accident only if I go into any script and see them there.

I like the option to save Incomplete executions to fix them later manually, but I don’t understand how I’m supposed to know about them.
Unlike the classic scheme where the script stops and I get an error email, Incomplete executions don’t create any notification anywhere.

I consider this a huge problem because my clients are losing orders and leads, and Incomplete executions are piling up in the script, but no information about it is given to me.
I didn’t realize this problem existed before because it runs in the background completely hidden and doesn’t show itself!

The option to switch to Sequential processing ON doesn’t work for me either, because the scenario doesn’t stop, but goes to PAUSED status. Notifications about this status also do not come correctly.

Have you encountered this problem? How can it be solved?

1 Like

Welcome to the Make community!

You can use the Break error handler module to attempt to retry modules that may fail with the same data again.

For more information, see

2 Likes


samliew
, Thank you for this information.
But the question is still open, I want to find out how to get Incomplete Execution notification. I want to be notified about problems in my scenarios, especially if they are not solved automatically.

In that case, your question might be a duplicate of Make Scenario Notifications and Scenario auto shutdown daily report

1 Like

Again, I thank you for your reply.
I already have such a scenario in place. It monitors the script statuses and if the status has changed to “disabled”, I get an instant notification.
But if you read my posts above carefully, it will be obvious that the script status does not change.
It is this problem in the product that I am pointing out.

There is an error in the scenario module → It does NOT stop → I do NOT get an alert → The error is NOT fixed → The script runs with errors → I find Incomplete executions by accident only if I go into any script and see them there.

So the tips suggested above are not useful. I will be glad if someone will pay attention to my question and understand its essence to fix this weakness in Make.com.

1 Like

Hi @Supagood,
Sorry I don’t have a solution, but thank you for raising the question.
I have the same issue with my scenarios with Incomplete executions when you accidentally notice that there is quite a queue there and it’s so frustrating that I don’t get notice.

Would be great to get a notification if the volume exceeds specific limit or they remain unresolved after X retries.

Agree. This question needs to be discussed better because people don’t know about the hidden executions in their scenarios.

1 Like

I faced with the same question.

That’s a great idea!

You can submit this suggestion to the Idea exchange, under Platform ideas. Don’t forget to search for it first, just in case someone already suggested it!

2 Likes

Extremely important issue

I am also facing the same issue

@Supagood did you ever manage to resolve this (or did Make develop a feature)? I’ve just run into the exact same problem and I didn’t spot it for a few days :frowning:

1 Like

Hey @danielfishknife, I have some ideas how to fix it or somehow to reduce the pay of this issue, but at this moment I can’t solve it too.

@Supagood I’ve built a scenario using the ‘List Scenario Incomplete Executions’ Make API call that sends a Slack message to a channel when it finds an unresolved incomplete execution for a specific scenario. Is that the sort of thing you’ve done too?

Yes, but in our company we have a complex monitoring system and my goal is to incorporate tracking of incomplete exectutions into it as well.
I will soon release a post about this to show the details

Its Too much theoretical present little bit example here or use case.
So it will be fun to resolve or may be community provide u temp. solution.

Hello there, I’ve made a post about monitoring and backup system here.

To find problems, we scan scenarios using the Make API call GET/dlqs. After that, only fresh errors were found, which should be fixed immediately.

I recommend creating the same logic in your system account to have an opportunity to find and fix hidden bugs in your scenarios immediately.
Please reply here if you need additional information!

1 Like