Slow print, many failed print jobs.

Hi

So we have been using Universal Print for a few months with varied results.

It sort of works, but to many times we see that printjobs can take several minutes, and often print jobs fails.

Strangley, when a print job failed, we just need to wait a few minutes and the job prints. If we restart a fails job, the printer prints the same job twice.

Today, I was trying to dig deeper and see if could find a reason for this behaviour.

In the connector log, I could see that when a job failed:

IPP Request operation: UpdateJobStatus
Uri: https://print.print.microsoft.com/printers/7a291562-2481-421b-bf5e-b51b63512317
response:StatusCode: 503, ReasonPhrase: 'Service Unavailable', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
  X-Cache: CONFIG_NOCACHE
  X-MSEdge-Ref: Ref A: 6EF26F23A4BD41FF929ECD4BE539A281 Ref B: HEL01EDGE1619 Ref C: 2021-10-13T08:28:32Z
  Date: Wed, 13 Oct 2021 08:28:34 GMT
  Content-Length: 0
}
Http client failed with statusCode: ServiceUnavailable
Exception of type 'ProxyLibrary.UPServiceException' was thrown.

Printer info:
(Name: 3206ci KX (XPS), CloudDeviceId: 7a291562-2481-421b-bf5e-b51b63512317, PhysicalDeviceId: 44e3c48e-acc3-49c1-a968-50addf981dbc.1127255732)
Request Details:
 Operation ID: UpdateJobStatus
Request ID: 1
Version: 2.0
Attributes:
Attribute Group: OperationAttributes
  Attribute attributes-charset: SimpleIppValue-Type:Charset-Value:UTF-8

  Attribute attributes-natural-language: SimpleIppValue-Type:NaturalLanguage-Value:en-gb

  Attribute output-device-uuid: SimpleIppValue-Type:TextWithoutLanguage-Value:urn:uuid:7a291562-2481-421b-bf5e-b51b63512317

  Attribute job-id: SimpleIppValue-Type:Integer-Value:2226


Attribute Group: JobAttributes
  Attribute generated-natural-language-supported - Multiple Values:
SimpleIppValue-Type:NaturalLanguage-Value:en
SimpleIppValue-Type:NaturalLanguage-Value:fr

  Attribute ipp-versions-supported - Multiple Values:
SimpleIppValue-Type:Keyword-Value:1.0
SimpleIppValue-Type:Keyword-Value:1.1
SimpleIppValue-Type:Keyword-Value:2.0

  Attribute printer-state: SimpleIppValue-Type:Enum-Value:3

  Attribute printer-state-reasons: SimpleIppValue-Type:Keyword-Value:none

  Attribute output-device-job-state: SimpleIppValue-Type:Enum-Value:9

  Attribute output-device-job-state-reasons: SimpleIppValue-Type:Keyword-Value:job-completed-successfully

  Attribute output-device-job-state-message: SimpleIppValue-Type:TextWithoutLanguage-Value:Completed

  Attribute job-impressions-completed: SimpleIppValue-Type:Integer-Value:1

  Attribute job-name: *** PII masked ***
  Attribute job-originating-user-name: *** PII masked ***
  Attribute microsoft-job-fetched-time-seconds: SimpleIppValue-Type:Integer-Value:63

  Attribute microsoft-job-processed-time-seconds: SimpleIppValue-Type:Integer-Value:0

  Attribute microsoft-job-printed-time-seconds: SimpleIppValue-Type:Integer-Value:21

  Attribute microsoft-output-device-job-state-message: SimpleIppValue-Type:TextWithoutLanguage-Value:
ErrorCode: 0
Impersonation: Disabled
AzureAdJoined : YES
EnterpriseJoined : NO
DomainJoined : NO
Successfully impersonated: N/A
Post impersonation user type: System
Print job origin: ReceivedNotification
Document format: application/oxps
File signature: PK

And then, the second entry

Retry 0 Exception: StatusCode: 503, ReasonPhrase: 'Service Unavailable', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
  X-Cache: CONFIG_NOCACHE
  X-MSEdge-Ref: Ref A: 6EF26F23A4BD41FF929ECD4BE539A281 Ref B: HEL01EDGE1619 Ref C: 2021-10-13T08:28:32Z
  Date: Wed, 13 Oct 2021 08:28:34 GMT
  Content-Length: 0
}

After a job fails, we can usually print the next one just fine. 

To me, it seems like the connector sometimes cant connect to print.print.microsoft.com

Any suggestions on how I should troubleshoot it from here?

EDIT: Looking at the Azure portal, I can see that the health status is "unknown"

Perhaps an issue in the connection between the PrintConnector and Azure services?