Deleting processing instance from API doesn't work

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

ddossot

Using Activity 5.13.

$ curl -v -X DELETE -u admin http://.../activiti-rest/service/runtime/process-instances/1401

HTTP/1.1 204 No Content
‍‍‍‍‍

Then:

$ curl -v -u admin http://.../activiti-rest/service/runtime/process-instances/1401

HTTP/1.1 200 OK
{
    "id": "1401",
    "url": "http://.../activiti-rest/service/runtime/process-instances/1401",
    "businessKey": null,
    "suspended": false,
    "processDefinitionId": "process:2:1206",
    "processDefinitionUrl": "http://.../activiti-rest/service/repository/process-definitions/process%3A2%3A1206",
    "activityId": "checkRequest",
    "variables": []
}
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Logs are clean: what am I doing wrong?

Alternatively in what tables should I manually delete rows to get rid of this instance?

ddossot

There was other strange behaviours like all edits to workflows in the Modeler were silently lost.

But I found out the root cause of the issue: I was using a different database for storing my JPA annotated entities. If I move these tables inside the database used by Activiti, everything works fine.

The surprising thing is that my entities were correctly hydrated from the other DB and most of Activiti was working, just some features were not working, but not reporting error either.

I guess the question is: is it possible to use two data sources, one for Activiti and one for custom entities persistence? I imagine the answer is yes and that I did something wrong with the configuration, but having an authoritative answer would be nice.