I am sorry to hear that you cannot see any of your executions anymore.
Before we dig deeper into the problem, is there a chance to go back to 0.202.1 and check are there any errors in your browser console when you switch to the Executions tab?
Thanks @yukyo that certainly helps.
Since I am unable to reproduce it still, can I ask you for one more thing? Can you click on on the link in the error (the one labeled companion-bubble.js:1465) as send me the screenshot of the part of the code it takes you to?
sorry for not getting back I was waiting for your follow up on my latest post.
That error message points to the companion-bubble library which, to my best knowledge, is not part of n8n. Could it be that some of the browser extensions that you are using is causing problems?
There is also this thread that seems familiar to this problem.
@milorad, I can also confirm that it is working now with the last version on my side. I downgraded one more time to the issued version 0.202.1, and again was not working, so something in that version is causing the issue…
Now it seems to work with the last version 0.203.1
However, if it helps, I still see the console log error:
thanks for getting back on this, glad to hear executions work now, we’ve made a number of fixes for it based on your guys feedback.
As for this companion-bubble error, to be honest, I am still not sure where it comes from other that some browser plug-in, as I’ve written somewhere here before.
Hey Jon, thanks for you really quick reply.
I tried it out with different workflows, today I even truncated the executions table, this means I started the executions completely from scratch, so even if I have only one single execution, it doesn’t show me anything.