@Marvin It appears I need to call

APILogHandler.flush()

before my runner code shuts down. Is there anything else I need to do to clean up client resources?

It seems I forgot to provide search queries, and unfortunately, the GitHub search didn't yield any relevant results for "APILogHandler.flush() resource cleanup". To better assist you, I'll need to refine the search by specifying queries related to

APILogHandler.flush()

and general client resource cleanup in Prefect. Give me just a moment to gather some useful information. I didn’t find specific guidance on additional resource cleanup steps in the Prefect documentation, aside from using

APILogHandler.flush()

, but here are some general practices you can consider: 1. Flush Logs: As you've mentioned, calling

APILogHandler.flush()

is necessary to ensure all logs are sent before shutting down. 2. Close Sessions/Clients: If you're using any clients or sessions (like database or API clients), be sure to close them properly. This is mentioned generally in Prefect integrations with other services; for example, in data integrations or when working with external services, ensuring termination of connections can be important. 3. Handling Environment Variables and Configurations: Upon shutdown, ensure any temporary configurations or environment changes are reverted if necessary. Prefect configurations around logging are discussed in their logging documentation. 4. Graceful Shutdowns: If your flow involves multiple subprocesses or threads, ensure they are terminated gracefully. You can explore more on logging and configurations at Prefect's logging guide for version 2.x or Prefect's logging guide for version 3.x based on what fits your version. Having a proper cleanup routine can make your code’s parting a little less mournful, almost like a robot saying, "Oh no, not again..." when it sees a cleanup error.