Enfocus Community

Reverse ask your bot, it already has the answer.

Hi old colleague :) I’ve seen these socket errors in all sorts of variations and across multiple Switch 2024 Fall servers, so at least you are not alone 8-) Most of the time it’s HTTP request (20.3), but indeed not exclusively; Unknown error Creating job error: socket hang up Unknown error Cannot ch...

Once I had a likewise Photoshop issue too: it wouldn't start processing. After heavily testing I came to the conclusion there's different behaviour that depends on the way Switch is started. It might help you too:
OS: Windows Server 2019 + Adobe Photoshop 2024!

Finally, we get to the problem. I take the command from test 3, which worked, and change the input and output to the J drive, which I already checked in test 2 and proved that CLI can access and write to the mapped share with no issue. However, when I run this command, I get the following error ret...

This settings work for me with HTTPS using a signed certificate.

I’ve encountered this exact same error with the HTTP request module. Initially, it appeared to occur randomly, but later I found that I could more or less trigger the error under heavy load. It took a while to debug but I got this response: "Apologies for the long delay, but I was told by the d...

Same here. It'll do that with Rename job 12.2 and the Search and Replace option.

It looks like it is a new 'feature' to make the warning log really useless:

That's very creative and really useful! I like it, thanks!

I already noticed: You have to be careful with this if you are clicking folders with a lot of jobs, the load time here will go up tremendously.

This is my internal powershell example flow/script, it shows all the magic

With Execute command you can run it like this: Edit: changed screenshot, makes more sense now

So relatable haha

+ 1 for the Jobs and Stats groups!

My personal priority would be jobs to be implemented first haha

I think there is a better chance of a response if you post in the PitStop forum