The job arrives quickly at Universal Print, but it takes a very long time for it to start printing.

%3CLINGO-SUB%20id%3D%22lingo-sub-2173328%22%20slang%3D%22ja-JP%22%3EThe%20job%20arrives%20quickly%20at%20Universal%20Print%2C%20but%20it%20takes%20a%20very%20long%20time%20for%20it%20to%20start%20printing.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2173328%22%20slang%3D%22ja-JP%22%3E%3CP%3EHi%2C%20All.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20trying%20to%20use%20Universal%20Print%20to%20try%20it%20out.%3C%2FP%3E%3CP%3EI%20have%20confirmed%20that%20the%20job%20will%20arrive%20in%20Azure%20as%20soon%20as%20I%20run%20print.%3C%2FP%3E%3CP%3EHowever%2C%20no%20matter%20how%20long%20I%20waited%2C%20the%20printed%20paper%20did%20not%20come%20out.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20a%20few%20hours%20of%20waiting%2C%20printing%20suddenly%20started%20and%20the%20paper%20came%20out.%20%3CBR%20%2F%3E%20The%20printed%20content%20was%20also%20normal.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20does%20it%20take%20so%20long%20to%20start%20printing%20after%20a%20job%20arrives%20in%20Azure%3F%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2208073%22%20slang%3D%22en-US%22%3ERe%3A%20The%20job%20arrives%20quickly%20at%20Universal%20Print%2C%20but%20it%20takes%20a%20very%20long%20time%20for%20it%20to%20start%20printi%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2208073%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F628681%22%20target%3D%22_blank%22%3E%40FIAformula1%3C%2FA%3E%20Are%20you%20using%20Universal%20Print%20connector%3F%20If%20yes%2C%20what%20version%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20use%20the%20latest%20version%20from%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FUPconnector%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2FUPconnector%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20continue%20to%20see%20issues%20with%20job%20latency%2C%20please%20file%20a%20support%20case%20with%20Azure%20Support%20portal.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi, All.

 

I am trying to use Universal Print to try it out.

I have confirmed that the job will arrive in Azure as soon as I run print.

However, no matter how long I waited, the printed paper did not come out.

 

After a few hours of waiting, printing suddenly started and the paper came out.
The printed content was also normal.

 

Why does it take so long to start printing after a job arrives in Azure?

Thanks.

3 Replies

@FIAformula1 Are you using Universal Print connector? If yes, what version?

 

Please use the latest version from https://aka.ms/UPconnector.

 

If you continue to see issues with job latency, please file a support case with Azure Support portal.

 

 

Hi,
I'm having this issue as well with our custom connector. We use long polling for notifications, but sometimes the job notification just won't arrive, so we are forced to also poll the notification endpoint every now and then to make sure the job is not delayed too much.

@Gianvito_Difilippo - seems like you are creating your own connector and having issues setting up notifications.

 

Where is your connector installed - is it in customer's network or in the cloud?

 

There are no known issues with notification service at this point of time. You may want to troubleshoot this internally. If still there is an issue, please reach out to support. They can help looking at logs and identify the problem with the print job.

 

Thanks

Saurabh