It seems that CloudManagerApi.cancelCurrentExecution() is asynchronously performed on the backend because even if that request succeeds a call to CloudManagerApi.startExection() with the same program and pipeline id directly afterwards fails with the following exception:
io.adobe.cloudmanager.CloudManagerApiException: Cannot create execution. Pipeline already running.
at io.adobe.cloudmanager.impl.CloudManagerApiImpl.startExecution(CloudManagerApiImpl.java:151)
at io.adobe.cloudmanager.impl.CloudManagerApiImpl.startExecution(CloudManagerApiImpl.java:140)
In the best case cancelCurrentExecution should be blocking, in the worst case it should be mentioned explicitly in the javadoc that this operation is performed asynchronously and there should be a poll mechanism being offered to wait for it to succeed.
It seems that
CloudManagerApi.cancelCurrentExecution()is asynchronously performed on the backend because even if that request succeeds a call toCloudManagerApi.startExection()with the same program and pipeline id directly afterwards fails with the following exception:In the best case
cancelCurrentExecutionshould be blocking, in the worst case it should be mentioned explicitly in the javadoc that this operation is performed asynchronously and there should be a poll mechanism being offered to wait for it to succeed.