If the bot is stopped using orchestrator, the current transaction will remain in-progress or will it get retry and gets to new and then ends the process?
Its all based on the exception we get buddy
–usually when a process built in REFramework is stopped using orchestrator it will iterate till GET TRANSACTION state…
–so when the process execution is before to that state then the queue item which is going to be processed wont get processed so will be in NEW status
–or if the process execution is after Should stop in Get TransactionData state and if it’s in PROCESS state then the set transaction status will be set to that queue item either like in progress or if it fails it will be retried
–but while retrying it self it will get stopped GET TRANSACTION state due to should stop activity
hope this would help you
To put a little more detail on what @Palaniyappan stated, the process continues to the next
Get Transaction Data state. To be precise, there is a
Check Stop Signal activity at the beginning of the
Get Transaction Data state that will check if Orchestrator has sent a stop request to the process. If it has been sent, the process will then set
Transaction Item = Nothing and as a result it will go to the
Final State and no further Transaction Items will be processed or moved to
Just highlighting what is actually stopping the process versus the number of ways it can stop based on it’s current state.
So when the transaction is in the process state and the Process is been stopped by the orchestrator then the transaction remains in progress, right?
The stop is passed in orchestrator when the flow is in process state
Yah till it meets should stop activity it will be in progress
Will it completes the complete process state or it directly goes to should stop activity
Yah It completes the process along the sequence and when it meets should stop activity on its way it stops there
Then how come the current transaction remains in-progess?
If current transaction completes the complete process state and set transaction status?
Yah usually when the process is in Process State and we have should stop in the very beginning of grt Transaction state
So now if we stop the process it will do all the process in Process state and then set the transaction and then it will reach for next item in get Transaction data state. As we have the should stop as a first activity in the get Transaction state it will stop there
So the process is executed, status is updated,and got stopped at get Transaction state though we tried to stop the process being at process state
Thank you… Please clarify this line
Till the execution meets the should stop activity the process will be executed
Oh okay now got it…
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.