Sorry this could go into the Bug Reports thread, but I have a feeling there could be a lot more here then just a simple bug. I was able to encounter a situation where I couldn’t load logs for a failed run:
I’ve improved the log messages that we receive in the server. If you try again and it re-occurs, I will hopefully have more information to debug this issue.
Just re-run it then with run id “48d5f6cdaec6c8aafbaf” (still got the same error as above), if you need some more time for your changes to propagate through I can re-run at a later too.
I created an automation using your function, and have been able to recreate the issue with the missing logs.
I was able to view the logs from my automation from within the system as it was running, and captured this screenshot. It errors and dumps the following stack trace:
It appears, though we don’t have definitive evidence, that it is the size of the logs being generated that is causing an issue. Our system is recording that 207Mb of logs are generated by the automation and then we encounter an error. Not conclusive that it is the large log size but an avenue of investigation for the moment.
Would you be able to reduce the log size generated by the Function to see if that helps?
Given the screenshot above, it may be that it is the error from the .Net library that is generating a lot of logs - without having looked at your source code, perhaps it is in a recurring/infinite loop that encounters an error on each iteration?
In the meantime we’ll investigate how to support larger log sizes.
