Orchestrator Issues 18.4

[mberkcavdar (Berk)]

Hello guys, these days we got trouble with orchestrator, whenever the transaction start it gets timeout and 524 error code and sometimes just an error occured messege

, we use 1 orchestrator and different 2 robots on the different 2 computers. We noticed especially 2 robots run at same time chance of getting these errors are widely increase. Is there any problem on orchestrator or we have different problem like firewall?

[loginerror (Maciej Kuźmicz)]

Hi @mberkcavdar

Could you see here?

Operation returned an invalid status code 'BadRequest'

Hi, Storing the value with such a large content in assets would not be a good practice. Assets in practice are to be used for storing configuration values and credentials. If this is transactional data then use queues to process. Regards, PD

It’s quite tricky to debug. I would suggest contacting our Technical Support.

[mberkcavdar (Berk)]

Update:

We build up Local Orchestrator on our servers. Nomore trouble with timeout issues.

Regards