Start process not working

Camunda 7 Topics Discussion & Questions
1

Hi,

I’m new in BPM engines and still learning it.
I watched the tutorial https://vimeo.com/235728986 and did the same stuff the only difference i figured out i have a tomcat server.

When i start now a process under the tasklist i get the notification process started but i see nothing in the cockpit.

Catalina.out print the LoggerDelegate but i dont see anything in the UI that something finished.

1 Like
2

Hi,

The community version doesn’t contain the history of the processes.
You can verify that your processes have been finished via the Rest API:
https://docs.camunda.org/manual/7.10/reference/rest/history/process-instance/get-process-instance-query/

3

Hi,

can you explain me why I see Invoice Receipt with a number of instances and my example is not growing with instances (when I start a process)?

4

Hi,

You can verify if you’re checking the correct process definition version.
Could you please share some screenshot examples and have a look at the server log file if something went wrong and there are some exceptions.

5

Model

48
48908×415 14.6 KB

6

Tomcat Catalina out

24
242930×608 384 KB

you see in the Log that the LoggerDelegate is fired but i get no running instance

7

I assume that it is already completed and that’s the reason you don’t see anything in Cockpit.
Have you executed the rest api endpoint which I mentioned?

8

Rest call to start the process

35
353282×1574 334 KB

9

Trying to get the process

44
443282×1554 286 KB

10

Hi @xAJ,

your process consists of only two service tasks. After starting your process the process neraly immediately finishes. So you have no chance to query the running instance because it is not running anymore. Here are two things you can do if you want to see something in your console:

  1. add a dummy element to your process that stops the process from completing automatically (e.g. add a user task or a timer event)
  2. dont query the running instances and rather query the history of the Camunda engine. Because your process finfishes immediately after starting it is not an active instance anymore and can be found in the history of all finished instances: REST API for History

Regards
Michael

2 Likes
11

Thanks with the rest history I got what i wanted :heart_eyes::ok_hand::+1:

Fast help thumps up :+1: