Desktop Agent has Warning "Connection has been Lost"

[Mino]

Hello.

I tried these steps.
https://help.sap.com/viewer/515fae5c9d04482d98c8fa9138975328/Cloud/en-US/eb62a00fd911425cb9bfc450d0c...

But an error occurred in the step 'Test the Scenario'.

Scenario 'Helloworkflow' could not be started

I checked Desktop Agent and there is a warning message.

At first, it is "Connection has been lost" and after test run "Not connected".

What should I check?

Regards,

Mino Kato

[raphaelberlth]

Dear Mino,

I've got the exact same issue here. Have you found any solution yet?

Thanks and kind regards,

Raphael

[Mino]

Dear Raphael,

I found it is just a network problem.
https://help.sap.com/viewer/9a34587e2f8b478b9b8a0e158f2b9215/Cloud/en-US/7caa6fb8fb8446b9b0636d72962...

But I can't find the cause.

Maybe our company-specific settings are interfering with the network, and only administrators can change the settings.
We try other PC(without our company security settings), the error has not occurred.
So we will use this PC for further testing.

Regards,

Mino Kato

[raphaelberlth]

Thank you Mino, I will get into contact with our IT.

Kind regards,

Raphael

[raphaelberlth]

Just to let you know, I found a solution which works well for my Desktop Agent without doing any changes in the network settings:

Within the Desktop Agent I added the same Tenant URL a second time with a different Tenant name, deleted the 'old' Tenant and renamed the new Tenant with the old name. Afterwards the connection problem was solved. Sounds strange, but at my Desktop Agent it worked well.

[Mino]

Thank you Raphael.

I tried it the same way and the connection problem was solved.
Amazing!

[Mino]

I found this document.
https://help.sap.com/viewer/9a34587e2f8b478b9b8a0e158f2b9215/Cloud/en-US/7caa6fb8fb8446b9b0636d72962...

● Connection has been lost (NEED_SENDING_CLIENT_INFO)

○ Cause: Cable unplug, WiFi disconnection...

○ Resolution: Check your connection, when it will be up Agent will reconnect automatically

Maybe this is just a network problem...
(But I can't find the cause.)