@Marvin Can you explain this error when trying to run concurrent deployments in parallel? 154459.516 | DEBUG | prefect.client - Encountered retryable exception during request. Another attempt will be made in 1.762195377774828s. This is attempt 1/6. Traceback (most recent call last): File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 60, in map_httpcore_exceptions yield File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 353, in handle_async_request resp = await self._pool.handle_async_request(req) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection_pool.py", line 253, in handle_async_request raise exc File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection_pool.py", line 237, in handle_async_request response = await connection.handle_async_request(request) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection.py", line 90, in handle_async_request return await self._connection.handle_async_request(request) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 112, in handle_async_request raise exc File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 91, in handle_async_request ) = await self._receive_response_headers(**kwargs) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 155, in _receive_response_headers event = await self._receive_event(timeout=timeout) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 205, in _receive_event raise RemoteProtocolError(msg) httpcore.RemoteProtocolError: Server disconnected without sending a response. The above exception was the direct cause of the following exception: Traceback (most recent call last): File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\prefect\client\base.py", line 216, in _send_with_retry response = await request() File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_client.py", line 1620, in send response = await self._send_handling_auth( File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_client.py", line 1648, in _send_handling_auth response = await self._send_handling_redirects( File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_client.py", line 1685, in _send_handling_redirects response = await self._send_single_request(request) File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_client.py", line 1722, in _send_single_request response = await transport.handle_async_request(request) File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 353, in handle_async_request resp = await self._pool.handle_async_request(req) File "\\v-tm-qeq-05\Prefect_Env\lib\contextlib.py", line 131, in exit self.gen.throw(type, value, traceback) File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 77, in map_httpcore_exceptions raise mapped_exc(message) from exc httpx.RemoteProtocolError: Server disconnected without sending a response. 154515.504 | DEBUG | prefect.client - Encountered retryable exception during request. Another attempt will be made in 1.956168415170509s. This is attempt 1/6. Traceback (most recent call last): File "\\v-tm-qeq-05\Prefect_Env\lib\asyncio\windows_events.py", line 457, in finish_recv return ov.getresult() OSError: [WinError 64] The specified network name is no longer available During handling of the above exception, another exception occurred: Traceback (most recent call last): File "\\v-tm-qeq-05\Prefect_Env\lib\asyncio\proactor_events.py", line 280, in _loop_reading data = fut.result() File "\\v-tm-qeq-05\Prefect_Env\lib\asyncio\windows_events.py", line 812, in _poll value = callback(transferred, key, ov) File "\\v-tm-qeq-05\Prefect_Env\lib\asyncio\windows_events.py", line 461, in finish_recv raise ConnectionResetError(*exc.args) ConnectionResetError: [WinError 64] The specified network name is no longer available The above exception was the direct cause of the following exception: Traceback (most recent call last): File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_exceptions.py", line 10, in map_exceptions yield File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\backends\asyncio.py", line 34, in read return await self._stream.receive(max_bytes=max_bytes) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\anyio\_backends\_asyncio.py", line 1212, in receive raise self._protocol.exception anyio.BrokenResourceError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 60, in map_httpcore_exceptions yield File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 353, in handle_async_request resp = await self._pool.handle_async_request(req) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection_pool.py", line 253, in handle_async_request raise exc File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection_pool.py", line 237, in handle_async_request response = await connection.handle_async_request(request) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection.py", line 90, in handle_async_request return await self._connection.handle_async_request(request) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 112, in handle_async_request raise exc File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 91, in handle_async_request ) = await self._receive_response_headers(**kwargs) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 155, in _receive_response_headers event = await self._receive_event(timeout=timeout) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 191, in _receive_event data = await self._network_stream.read( File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\backends\asyncio.py", line 36, in read return b"" File "\\v-tm-qeq-05\Prefect_Env\lib\contextlib.py", line 131, in exit self.gen.throw(type, value, traceback) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_exceptions.py", line 14, in map_exceptions raise to_exc(exc) httpcore.ReadError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\prefect\client\base.py", line 216, in _send_with_retry response = await request() File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_client.py", line 1620, in send response = await self._send_handling_auth( File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_client.py", line 1648, in _send_handling_auth response = await self._send_handling_redirects( File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_client.py", line 1685, in _send_handling_redirects response = await self._send_single_request(request) File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_client.py", line 1722, in _send_single_request response = await transport.handle_async_request(request) File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 353, in handle_async_request resp = await self._pool.handle_async_request(req) File "\\v-tm-qeq-05\Prefect_Env\lib\contextlib.py", line 131, in exit self.gen.throw(type, value, traceback) File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 77, in map_httpcore_exceptions raise mapped_exc(message) from exc httpx.ReadError 154515.690 | DEBUG | prefect.client - Encountered retryable exception during request. Another attempt will be made in 1.9267586944460113s. This is attempt 1/6. Traceback (most recent call last): File "\\v-tm-qeq-05\Prefect_Env\lib\asyncio\windows_events.py", line 457, in finish_recv return ov.getresult() OSError: [WinError 64] The specified network name is no longer available During handling of the above exception, another exception occurred: Traceback (most recent call last): File "\\v-tm-qeq-05\Prefect_Env\lib\asyncio\proactor_events.py", line 280, in _loop_reading data = fut.result() File "\\v-tm-qeq-05\Prefect_Env\lib\asyncio\windows_events.py", line 812, in _poll value = callback(transferred, key, ov) File "\\v-tm-qeq-05\Prefect_Env\lib\asyncio\windows_events.py", line 461, in finish_recv raise ConnectionResetError(*exc.args) ConnectionResetError: [WinError 64] The specified network name is no longer available The above exception was the direct cause of the following exception: Traceback (most recent call last): File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_exceptions.py", line 10, in map_exceptions yield File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\backends\asyncio.py", line 34, in read return await self._stream.receive(max_bytes=max_bytes) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\anyio\_backends\_asyncio.py", line 1212, in receive raise self._protocol.exception anyio.BrokenResourceError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 60, in map_httpcore_exceptions yield File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 353, in handle_async_request resp = await self._pool.handle_async_request(req) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection_pool.py", line 253, in handle_async_request raise exc File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection_pool.py", line 237, in handle_async_request response = await connection.handle_async_request(request) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection.py", line 90, in handle_async_request return await self._connection.handle_async_request(request) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 112, in handle_async_request raise exc File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 91, in handle_async_request ) = await self._receive_response_headers(**kwargs) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 155, in _receive_response_headers event = await self._receive_event(timeout=timeout) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\http11.py", line 191, in _receive_event data = await self._network_stream.read( File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\backends\asyncio.py", line 36, in read return b"" File "\\v-tm-qeq-05\Prefect_Env\lib\contextlib.py", line 131, in exit self.gen.throw(type, value, traceback) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_exceptions.py", line 14, in map_exceptions raise to_exc(exc) httpcore.ReadError

Your message was too long by 3026 tokens - please shorten it and try again. For reference, here's your message at the allowed limit:

Can you explain this error when trying to run concurrent deployments in parallel?

154459.516 | DEBUG | prefect.client - Encountered retryable exception during request. Another attempt will be made in 1.762195377774828s. This is attempt 1/6. Traceback (most recent call last): File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 60, in map_httpcore_exceptions yield File "C:\Users\cleung\AppData\Roaming\Python\Python38\site-packages\httpx\_transports\default.py", line 353, in handle_async_request resp = await self._pool.handle_async_request(req) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection_pool.py", line 253, in handle_async_request raise exc File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection_pool.py", line 237, in handle_async_request response = await connection.handle_async_request(request) File "\\v-tm-qeq-05\Prefect_Env\lib\site-packages\httpcore\_async\connection.py", line 90, in handle_async_request return await self._connection.handle_async

@Marvin Can you explain this error when trying to run concurrent deployments using run_deployment? 154515.690 | DEBUG | prefect.client - Encountered retryable exception during request. Another attempt will be made in 1.9267586944460113s. This is attempt 1/6. Traceback (most recent call last): File "\\v-tm-qeq-05\Prefect_Env\lib\asyncio\windows_events.py", line 457, in finish_recv return ov.getresult() OSError: [WinError 64] The specified network name is no longer available

Based on the information obtained from the Prefect documentation and GitHub issues, the error you're encountering seems to be about an operational issue on Windows related to network connectivity, rather than a specific issue with Prefect itself. The Windows error "The specified network name is no longer available" may indicate intermittent network connectivity problems or issues with file sharing over a network. There wasn't a direct hit in the Prefect documentation or open GitHub issues that explain how to resolve this problem in the context of running Prefect deployments. However, I can provide some general advice: 1. Check Network Stability: Ensure the network connection is stable. Intermittent network issues can cause failure in connections to remote resources. 2. File System Permissions: If Prefect deployment operations involve accessing shared network resources or writing to a network drive, ensure that the correct permissions are in place and the resource is available. 3. Retry Logic: The debug output you provided mentions an "Encountered retryable exception". Ensure that the retry logic is appropriate and robust enough to handle transient network issues. 4. Prefect Community: If you continue to experience issues, consider reaching out to the Prefect community or support. 5. Local Network Troubleshooting: Since this appears to be a network-related issue, you might need to perform local troubleshooting steps, such as restarting your network adapter, ensuring file sharing is enabled appropriately in Windows settings, or contacting your network administrator for further assistance. Given that this could be an environment-specific issue not directly tied to Prefect, the resolution might involve debugging networking on your specific setup or increasing robustness around network-related operations in your deployment scripts. Since there wasn't a clear technical solution related to Prefect, you might want to explore general Windows network troubleshooting steps further: - Restart the affected systems. - Check for any recent changes on the network that might affect connectivity. - Confirm that the network path in question is correct and accessible. Although not directly related to Prefect, here are links to the Prefect documentation for further reading: - Deployments Tutorial - Concepts: Deployments - Getting Started: Quickstart And unfortunately, there were no relevant open issues found in the GitHub search that matched your problem, indicating that this might not be a common or known issue within the Prefect community. Please consider reaching out to Prefect's community forum or support channels if you need more specific assistance with Prefect and concurrent deployments.