• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 6 subscribers
  • Views 8789 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Process

Start Process Smart Service failing though Process Instance is being triggered

sikhivahans
I am triggering a Process Instance by using 'Start Process Smart Service'. A weird behavior I have noticed is, the Process Instance is being triggered but the Start Process Smart Service is crashing with an error. The target process model has just two parameters out of which one is of type CDT(single) and other is of type Date (single). I can also clearly see the triggered instances, the parameterised variables in triggered instances populated with values configured in the Start Process Smart Service node.

Content from logs is as follows:
UnattendedJavaActivityRequest] ERROR com.appiancorp.process.engine.UnattendedJavaActivityRequest - An error occurred while executing activity: id=536936184, classname=com.appiancorp.process.runtime.activities.StartProcessSmartService2
12:39:25,568 INFO [stdout] (Appian Work Item - 6406 - Proce...

OriginalPostID-240702

  Discussion posts and replies are publicly visible

Parents
  • 0
    @chetany As said earlier, it seemed to me that it's waiting for something (similar to the synchronous call) and I agree with your theory as I understood in a similar way finally after few trails. But an asynchronous call shouldn't really care about the configurations in the first place. For instance when we trigger a process using messaging or sub-process node, the activity chain in the target process model will be ignored. Also as said earlier, if this(what we are discussing about) behavior proves to be true/valid, the target model should be an asynchronous wrapper over the synchronous model(if the model is intended to be activity chained) which is not desirable.

    Anyways, as mentioned by @dcooke, this is an issue and we have raised a support ticket for the same.
Reply
  • 0
    @chetany As said earlier, it seemed to me that it's waiting for something (similar to the synchronous call) and I agree with your theory as I understood in a similar way finally after few trails. But an asynchronous call shouldn't really care about the configurations in the first place. For instance when we trigger a process using messaging or sub-process node, the activity chain in the target process model will be ignored. Also as said earlier, if this(what we are discussing about) behavior proves to be true/valid, the target model should be an asynchronous wrapper over the synchronous model(if the model is intended to be activity chained) which is not desirable.

    Anyways, as mentioned by @dcooke, this is an issue and we have raised a support ticket for the same.
Children
No Data

© 2024 Appian. All rights reserved.