Idea ID: 1649696

SM - OO Integration: the API recognizes only error and success status while OO has more than 6 statu

Status : Waiting for Votes
over 3 years ago

Details 

The current integration of SM and OO handles only the error and success result status returned by OO API (execution log summary), see attachments.

This logic needs to be enhanced in order to consider all the other status of the OOexecution :

The integration in the SM side should manage all of these OO flow statuses (see attachments).

Scenario & impact

- A use case is that when the flow gets into other status (like Paused, User Input required, Cancelled...) , the SM task remains in execution phase (in progress), and the associated record in AutomationTaskUpdate will not be handled and deleted (refresh Status done by SM to get the execution log status).

=> User action is then needed in SM or OO in order to unlock the record.

 The intergation should also handles 2 other scenarios:

-A timeout need to be implemented on SM side to handle the locked flows and consider it as ended with error, so that the Automation Task is moved to the next phase.

The user can decide to execute again..

- When the Run ID is not available anymore , or the request sent by SM to get the OO execution status , gets invalid (404 error for example), the SMOOAutomationTask process /schedule goes in error (schedule AutomationTaskUpdate), and the SM admin should detects which records in this table is causing the issue and restart the schedule each time.

 

Scenario

 

- A use case is that when the flow gets into other status (like Paused, User Input required, Cancelled...) , the SM task remains in execution phase (in progress), and the associated record in AutomationTaskUpdate will not be handled and deleted (refresh Status done by SM to get the execution log status).

=> User action is then needed in SM or OO in order to unlock the record.

 

Workaround 

A timeout has been implemented to set the execution status to error after a period of time.

 

Unacceptable 

It is all about Automation. We need to automate and monitor the full execution between SM and OO;

Manual user actions are not acceptable to diagnoses OO execution on SM side . OO Tasks/flow on SM side should handle failure/locks/timeout...

 

Required

see description above

Tags: