Scenario Execution history

:bullseye: What is your goal?

Being able to debug and search errors again in an efficient way.

:thinking: What is the problem & what have you tried?

I dont know when it changed but since some time when i have a look in previous runs (even new ones from the same day) i often dont see every modules output.

Sometimes modules are even invisible - path to or from the module is visible but the module itself is not.

Is this a bug or a change to make? Because it makes debugging in some cases imposible.

:clipboard: Error messages or input/output bundles

.

1 Like

Hey Andreas,

can you show some screenshot highlighting what you mean? If you edited the scenario, then modules will be missing completely. And if a bundle didn’t pass a filter, they will be grayed out, but shouldn’t be invisible.

But, yeah a hole in the flow with a completely invisible module in between should be reported directly to the Make team.

Here for example - the SFTP Module had an error but in the history it does not show the output of any previous module.

I will have a look for an example of the other error i described.

Basicly it was a rather big scenario and when i opened the run it showed everything but the root module which was a webhook. So i had no chance to see the input :-/

1 Like

Ok this is most likely a validation error. Maybe the connection expired? You should be able to click on it and see what’s the exact error message.