Process runs successfully in Studio, but not on Portal

Q&A
1

I’m writing a process in 7.1.5. It runs successfully in my Studio, but a human task that is a manager approval form fails on my Tomcat-based portal without any description of why it fails. I’ve set org.bonitasoft.level = FINEST in logging.properties, but I can’t seem to get any logging info on why the task is failing. I can’t seem to collect any info on the failure, nor does any show up on the failed case’s “More” screen. Any help would be greatly appreciated!

2

I know it has failed because if I log in as an administrator it shows up in the Failed Processes area. I know it fails during the human task because the two tasks before and after it are tasks that execute an smtp connector. I have connector logging turned up, and the first email task shows up in the bonita.log file. The task just after does not show up at all. And I get the first email just fine.

Before I posted this, I did just what you said – I cleaned out the log files so that only this one process’ stuff would be in it. Nothing helpful appears. No exception info shows up at all. Isn’t there a way to get more logging out of a human task?

3

Thanks for your suggestions, Sean and Antoine. I didn’t want to take your time (I’m sure you are busy solving many problems), and the process wasn’t very large. So I re-created it from scratch. The failure disappeared… I suspect it was a problem with a form. I read in the latest 7.1.5 readme that you can’t create a form by building it in the UI first. Rather, you have to create it from within the task itself. I had built mine in the UI. Maybe that had caused the problem.

Phil

4

If there are no messages to say it has failed, how do you know it fails?

Have you logged on to the managers profile to see that the next step exists? Are you sure it’s starting?

First step:
Close the portal down
delete the existing logs (or save them somewhere)
Restart the portal
execute the process
check the logs.

That way you only have this execution to deal with…

regards
Seán

5

are you able to share it so I can have a look?

6

For testing purpose I can recommend to configure connector execution error handing to “ignore error”. That might help to isolate the error cause in case it’s related to connectors.

Also as task is for manager I’m assuming you have an actor filter configured. You might want to try to remove the filter in case execution of the filter failed.

Also I suggest by Sean, I would be really interested in getting your process definition so I can reproduce the issue and figure out which logs might need improvement.

7

Great news! Thanks for taking the time to update us :wink: