Skip to main content
Solved

Process flow not started when task is called through indicium API

  • October 31, 2025
  • 3 replies
  • 58 views

Forum|alt.badge.img

Good afternoon,

I have a task that is the start of a simple process flow, which starts some more tasks and writes a report.

The task will be started with a http call to indicium. I thought the process flow would trigger when i http call this task but it doesn’t, it only executes the task I am calling. There are no errors in indicium.

The process flow works if i change the first task to a table task and start it in the application

 

I managed to get a set up like this working in the past, but I dont know what I am missing here, does anyone know? Thanks

Kind regards, Dennis

Best answer by Erwin Ekkel

The start task could require user input. So you probably have to manually guide the flow: 

 

  • If the process flow reaches a process action that requires client input, then Indicium will return a 201 Created together with a Location header that points to the pending process action. The client can continue the process flow by sending a POST request to the continue endpoint of this pending process action.

3 replies

Forum|alt.badge.img+17
  • Moderator
  • October 31, 2025

Start task is not a system flow action. To run tasks automatically you need to change them to Execute System Task instead. 


Forum|alt.badge.img+17
  • Moderator
  • Answer
  • October 31, 2025

The start task could require user input. So you probably have to manually guide the flow: 

 

  • If the process flow reaches a process action that requires client input, then Indicium will return a 201 Created together with a Location header that points to the pending process action. The client can continue the process flow by sending a POST request to the continue endpoint of this pending process action.

Forum|alt.badge.img

I got a 200 OK code back from postman so it seems the process flow was not started at all by calling the first task.

 

But I do have it working now and it did have to do with user input: the tasks after the first one have to be execute system task actions.

I guess because the user input of the first task is the http body and subsequent tasks dont have any, they get their parameters from the process flow input variables.