Connection failed: Returned by server pipeName is null

[mogikanin]

Describe the bug

Hi, we have a some amount of such exceptions on our production. Not so many (less than 1% of users), comparing to entire installations count. As usual we never got this exception locally :)
System.InvalidOperationException: Connection failed: Returned by server pipeName is null.

Here the stack trace

System.InvalidOperationException: Connection failed: Returned by server pipeName is null
File "//src/libs/H.Pipes/PipeClient.cs", line 301, col 17, in async Task PipeClient.GetConnectionPipeName(CancellationToken cancellationToken)
File "//src/libs/H.Pipes/PipeClient.cs", line 304, col 13, in async Task PipeClient.GetConnectionPipeName(CancellationToken cancellationToken)
File "/_/src/libs/H.Pipes/PipeClient.cs", line 176, col 13, in async Task PipeClient.ConnectAsync(CancellationToken cancellationToken)

We use wpf client to windows service communication (both .net 6). Exception occurs on client side.
Do you have any ideas why this may happen, and what is better solution to deal with it? I'm almost sure this is a some edge case when Windows or our service is shutting down, so I'm thinking simply wrap PipeClient.ConnectAsync() into try/catch and ignore this exception.

Thanks in advance!

[HavenDV]

Yes, it seems your solution is the most optimal, I'm not sure that separate processing at the library level is required here