I am currently evaluating Make.com as a potential alternative to Zapier, where I have been an active customer for some time. One of the key features I greatly rely on in Zapier is the comprehensive execution history it provides. Specifically, Zapier allows me to view detailed data for each step of an automation—including the input data received, the output data passed to subsequent steps, and the complete responses returned by external services.
While exploring Make.com, I noticed that the execution history appears to provide only high-level metadata. I have not yet been able to locate detailed step-by-step data—such as the actual payloads passed between modules and the responses received—which is crucial for troubleshooting and debugging purposes.
In our use case, some steps within our scenarios occasionally fail. In such instances, it is imperative for us to be able to:
- Inspect the exact data that was received at each step.
- Understand what went wrong during the execution.
- Replay the scenario using the same data set to verify fixes or adjustments.
Could you please guide me on how to access this level of detail within Make.com? Additionally, is there a built-in feature to facilitate the replaying of failed or completed executions using the original data?
Any guidance or best practices you can provide would be greatly appreciated.
Hey there,
not sure what you checked but Make does provide this data. Select a scenario → go to History → click on Details next to an execution you want to check. Click on the bubble next to each module to see exactly what data it received and what data it sent (you can also export these as JSONs from the same window) or click on the modules themselves for a different view of the data.
Also you can retry an execution with the same data, provided it errored out. Just press the run button or enable the scenario, it will then prompt you if you want to use the stored executions or delete the queue and start fresh.
On a side note, all of this is available in the Make Academy.
Thank you so much for your response. I was able to find the data in the history section like you suggested.
I was also able to retry an execution but
- it’s only available for errored out cases like you mentioned. It would have been if all cases were available because we need to reprocess data often times.
- If 8 cases failed, I cannot play 5th one only it seems. Is there any way to decide which one to execute?
About the first point - I think Make are currently working on this, but at the moment it is not easily available. Depending on the scenario, you can go to the history of the specific execution, copy the input bundle from the trigger module and resend that data to essentially retrigger the same run.
About the second point - there is an execution queue based on when the events arrived. You can access it and delete executions you dont want to run, but I dont think its possible to rearrange it at the moment. But if its a function you need, you can add a suggestion here.