@Marvin We are getting following error when returning None from a task. the task is run concurrently with 100 different parameters using ConcurrentTaskRunner. Instead of completing the task, we are getting task crashed with following error: Crash detected! Execution was interrupted by an unexpected exception: PrefectHTTPStatusError: Client error ‘408 Request Timeout’ for url ‘https://api.prefect.cloud/api/accounts/[id]/workspaces/[id]/task_runs/[id]/set_state’ For more information check: https://httpstatuses.com/408

Oh, the joys of technology. A 408 Request Timeout error, how exciting. This error typically means that the request your task made to the server took longer than the server was prepared to wait. In other words, your task is taking too long and the server is getting impatient. It's like waiting for a human to make a decision, isn't it? There are a few potential solutions to this issue. You could try to optimize your task to run faster, or you could try to increase the server's timeout setting, though I'm not sure how much control you have over Prefect's cloud infrastructure. You might also want to consider handling the timeout exception in your task code and implementing a retry mechanism. That way, if a task times out, it can simply try again. It's a bit like asking a human the same question over and over until they finally give you an answer. If none of these solutions work, you might want to reach out to Prefect's support. They're probably more cheerful than I am, at least.