Killed Process

32 views
Skip to first unread message

huw.wa...@gmail.com

unread,
Jul 30, 2018, 10:22:38 AM7/30/18
to Fujitsu RunMyProcess Developer Community
Good Afternoon,

We have come across a killed process within our process reports.

We are getting the following error:

2018-07-30T14:02:28+0000 - Join "" (id: 83 - status: COMPLETED): Maximum execution time exceeded (300000 ms)

The visual representation of the process shows that the gateway with ID 83 has a status of completed.

The process is showing a status of aborted at another activity, however, when I try and restart the process at this activity, I can the above error.

Please can you advise as to why the process has been killed as the documentation does not contain any information that describes this status? Could you also advise as to how we may restart the process.

Thanks,

Huw

Pankaj Kumar

unread,
Jul 30, 2018, 11:23:22 AM7/30/18
to Fujitsu RunMyProcess Developer Community
Hi Huw,

Since this is project/application specific query, we kindly request you to contact RunMyProcess Support Portal to raise a ticket, please find the url to access RunMyProcess Support Portal as below:-

Also kindly share details as account id,  project name. process instance id, error details, approx date and time when this issue occur.



Thank you,
Pankaj Kumar
Fujitsu RunMyProcess Support


--
Fujitsu - RunMyProcess
---
You received this message because you are subscribed to the Google Groups "Fujitsu RunMyProcess Developer Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supportforum+unsubscribe@runmyprocess.com.
To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at https://groups.google.com/a/runmyprocess.com/group/supportforum/.
To view this discussion on the web visit https://groups.google.com/a/runmyprocess.com/d/msgid/supportforum/49543d6c-ec80-43c9-b366-9d9bbabb663c%40runmyprocess.com.
For more options, visit https://groups.google.com/a/runmyprocess.com/d/optout.

Reply all
Reply to author
Forward
0 new messages