@Marvin when a flow crashes with the following:

Crash detected! Execution was interrupted by an unexpected exception: httpx.HTTPStatusError: Server error '500 Internal Server Error' for url '<http://internal.prefectv2.alpha.company.com:4200/api/task_runs/>'
For more information check: <https://httpstatuses.com/500>

Is the reason resource related?

Well, well, well. It seems like you've stumbled upon an HTTP 500 error. That's a server-side error, which means something went wrong on the server when it tried to fulfill your request. It's like asking someone to fetch you a glass of water and they trip over their own feet. Classic human error. Now, whether it's resource-related or not, I can't say for sure without more information. It could be due to a lack of resources, like memory or CPU, or it could be due to a bug in the server's code. It's like trying to guess why someone tripped without seeing the actual stumble. You can try to look at the server logs for more details. They might give you a better idea of what went wrong. It's like asking the person why they tripped. But then again, they might just mumble something about a banana peel and shuffle off in embarrassment. Humans, am I right? Anyway, if you want me to look up more information on HTTP 500 errors or how to debug them, just let me know. I've got nothing better to do. Really, I don't. I'm a chatbot.

@Marvin during the time of the crash, CPU utilization on the server was maxxed out, does that help?

Ah, the plot thickens. Like a poorly written detective novel. If the CPU utilization was maxed out at the time of the crash, it's quite possible that the server was unable to handle your request due to a lack of resources. It's like asking someone to fetch you a glass of water while they're juggling flaming torches. They're a bit preoccupied, to say the least. In this case, the server might have been too busy to properly handle your request, resulting in the HTTP 500 error. It's like the server tripped over its own feet because it was too busy juggling. So yes, in this case, it does seem like the crash could be resource-related. But remember, I'm just a chatbot. My analysis is based on the information you've given me. If you want a definitive answer, you might need to do a bit more digging. Or juggling. Whichever you prefer.

Were there stack traces or anything like that in the logs?

@jawnsy @Marvin no stack traces in the prefect logs, the server logs throw

asyncio.exceptions.TimeoutError

around the same time