Jobs not finishing

Product: PowerShell Universal
Version: 3.3.4

We are occasionally seeing jobs never finish. Below we have a job that has been running for almost 15 hours.


Job shows its completed but still running?

Also its showing that there is pipline output

Not sure if it matters but it is a nested job that was stuck.

Force rebooting the psu service the job shows failed now with this error.

@{error=Status(StatusCode="Unavailable", Detail="failed to connect to all addresses", DebugException="Grpc.Core.Internal.CoreErrorDetailException: {"created":"@1664369610.470000000","description":"Failed to pick subchannel","file":"..\..\..\src\core\ext\filters\client_channel\","file_line":3218,"referenced_errors":[{"created":"@1664369610.470000000","description":"failed to connect to all addresses","file":"..\..\..\src\core\lib\transport\","file_line":165,"grpc_status":14}]}"); line=} 

Can you please let me know if you see a hangfire job listed when this happens?

Will do

We are running into issues where our ticketing system drops calls if the endpoint/api doesnt respond within 30 seconds. This is something we can not change. We sometimes have 10+ endpoint calls which fires off other psuscripts and it crushes the servers CPU with external pswh processes. When the CPU is pegged endpoint calls tend to hang.

We are just looking at better ways of integrating these jobs with out ticketing system.


Interesting. If you wanna have a quick chat about this, let me know. I’d be curious to understand a little more about the issue.

I think that would be very beneficial for us. Would you like me to put in a support ticket for this?

Let me know when you have some time, I should be have some time tomorrow as well.

Yes, please. Next week will work better for me.

Hey Adam,

we had another one of these jobs that never finished… I will put in a support ticket for this.

1 Like