Task Republishing and Feedback Loop for Orchestrator

[maximilianong]

Description

This feature aims to enhance the interaction between the orchestrator and the golden record process by introducing a feedback loop for sharing members and providing functionality to republish tasks. Additionally, it includes the ability to manage tasks stuck in specific states within the orchestrator.

Key Functionalities

Feedback Loop for Solved Tasks:

• Enable sharing members to provide feedback on tasks that have been processed by the golden record service.
• Allow sharing members to report errors or issues with the processed data sets.

Republishing Tasks:

Provide an option for sharing members to republish data sets with the same task back to the golden record process if issues are identified.

State Management for Stuck Tasks:

Implement functionality in the orchestrator to move tasks between states, specifically for tasks stuck in 'PoolSync' and 'Reserved' states.

Implementation Details

Feedback Loop:

• Feedback Interface: Develop a user interface for sharing members to submit feedback on processed tasks.
• Feedback Submission: Implement backend services to handle feedback submissions, including error reporting and suggestions for improvements.
• Feedback Processing: Integrate feedback processing within the golden record service to review and act upon the feedback received.

Republishing Tasks:

• Republish Option: Add an option in the feedback interface for sharing members to republish data sets with the same task.
• Task Re-queueing: Modify the golden record service to accept republished tasks and place them back into the processing queue with appropriate priority.

State Management for Stuck Tasks:

• State Transition Interface: Develop an interface within the orchestrator to allow administrators to manually move tasks between states
• State Transition Logic: Implement backend logic to handle state transitions, ensuring data integrity and consistency.
• Monitoring and Alerts: Introduce monitoring tools to detect tasks stuck in 'PoolSync' and 'Reserved' states and alert administrators for manual intervention.

Additional information

Contribution will be done by @nicoprow Committer to support this will be @SujitMBRDI / @nicoprow / @maximilianong

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning
• Please add missing sections from the feature template

[stephanbcbauer]

Since this feature was not presented in the Open Planning ⇾ I will add the status “not in release” ⇾ if this feature is planned for 25.03, let's talk. If it is planned for 25.6, please add the label and set the status back to Inbox.