@Marvin When running flow.from_source(), Im getting this error when I import variables Exception ignored in: <function _ProactorBasePipeTransport.del at 0x0000021FC5BE3EE0> Traceback (most recent call last): File "W:\lib\asyncio\proactor_events.py", line 116, in del self.close() File "W:\lib\asyncio\proactor_events.py", line 108, in close self._loop.call_soon(self._call_connection_lost, None) File "W:\lib\asyncio\base_events.py", line 751, in call_soon self._check_closed() File "W:\lib\asyncio\base_events.py", line 515, in _check_closed raise RuntimeError('Event loop is closed') RuntimeError: Event loop is closed

The error you're encountering,

RuntimeError: Event loop is closed

, typically occurs when an asyncio event loop is closed prematurely or improperly. This can happen if the event loop is closed while there are still tasks or callbacks pending. Here are a few steps and considerations to address this issue: 1. Ensure Proper Event Loop Management: - Make sure that you're managing the asyncio event loop correctly. If you're using

asyncio.run()

, it should be the top-level function that drives your asyncio program. Avoid calling

loop.close()

manually if you're using

asyncio.run()

. 2. Check for Nested Event Loops: - If you're running this code in an interactive environment (like Jupyter notebooks or certain IDEs), ensure that you're not inadvertently creating nested event loops. This can happen if the interactive environment already has an event loop running. 3. Review Flow Execution Context: - Ensure that the flow is being executed in an environment that properly supports asyncio operations. Prefect's flow execution should handle this, but if you're integrating with other systems or running in a unique environment, double-check the event loop handling. 4. Prefect Version: - Make sure you're using a compatible version of Prefect and check for any known issues or updates related to flow execution and asyncio handling. You can review the Prefect repository for any related issues. 5. Example Usage: - If possible, review examples from the Prefect documentation or repository to ensure that your usage aligns with recommended patterns. If you continue to face issues, consider providing more context or code snippets for further assistance.