but with ‘process-definition put suspend api’, response status is 204 and ‘Get process-definition’ is like this:
(if execute previous APIs by this id & key)
id: "invoice:1:355b7099-b424-11ec-af2f-caff283c2eeb"
key: "invoice"
name: "Invoice Receipt"
resource: "invoice.v1.bpmn"
startableInTasklist: true
suspended: false //<======= not ok. do not affect!
(other api like ‘suspend process instance’, working well at the same time.)
So make sure that you are starting your Camunda instance with the REST API’s enabled, and also start it with the SwaggerUI enabled.
With the swaggerUI enabled, you can go to http://localhost:8080/swaggerui and get direct access to the REST APIs for testing. See if you can get the commands to work via that method. If they are returning any errors, etc, please post them here so we can help you track them down.
Those two APIs do different things. The one that I sent suspends a specific process instance whereas the one you’re using suspends an entire process. Those two things are not the same. An instance is a particular running job process. Suspending the entire process means that you won’t be able to start new instances of the process until you un-suspend the process.
So I think it’s important to decide which you are actually trying to accomplish, and then use the appropriate API.
But as i test it by Postman, this working if and only if we remove executionDate in body.
And your reply(solution) worked, because the curl haven’t executionDate in body.