Control Tower process publishing error

Scope of problem:

We have a WF Intelligent Automation Cloud Enterprise v 2.4.0 (both “Studio” and “Server” components) installed on a Virtual machine, running Windows Server 2012 RDS. Several days ago, upon attempting to update a Bot task, previously published to Control Tower, we faced the following error:

image

Attempts of publishing new business process elements to Control Tower (Both recordings and Bot Tasks) lead to similar error. For example, trying to publish a new Bot Task, we faced the following error:

Error occurred while publishing Bot Task to Control Tower.

Reason: .… Failed with status code: 403

image

The Control Tower component functions properly. The previously published Bot Tasks and Business processes are successfully launched and executed.

In order to find solution to the problem, we have:

  1. Checked our Server profile settings: the credentials are identical to the ones used to log in the Control Tower. The problem hasn’t been solved. The screenshot of our Server Profile settings is attached hereby:

image
image
image

  1. Have attempted to Run WF software as Administrator, which did not help as well.

The questions:

  1. Would you kindly advise us on any potential reasons for such error to occur?
  2. Would you kindly provide us with a solution to the Control Tower script publishing problem we have faced?

Thanks in advance!

We have the same issue, when we published a business process.
please help us.
.
com.workfusion.studio.mediator.service.domain.CommunicationException: Failed with status code: 500
com.workfusion.studio.mediator.service.domain.CommunicationException: Failed with status code: 500
java.lang.RuntimeException: com.workfusion.studio.mediator.service.domain.CommunicationException: Failed with status code: 500
at com.workfusion.studio.rpa.wizard.ExportWebharvestConfigAsNewProcessWizard.lambda$0(ExportWebharvestConfigAsNewProcessWizard.java:99)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
caused by com.workfusion.studio.mediator.service.domain.CommunicationException: Failed with status code: 500
at com.workfusion.studio.service.AbstractRestService.execute(AbstractRestService.java:41)
at com.workfusion.studio.service.RestExportConfigService.pushToNewProcess(RestExportConfigService.java:48)
at com.workfusion.studio.rpa.wizard.ExportWebharvestConfigAsNewProcessWizard.lambda$0(ExportWebharvestConfigAsNewProcessWizard.java:97)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)