You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The orchestration service needs to know when and where an eCR message has failed in the pipeline and send that failure with the run data to the eCR Viewer for storage
🤔 Why it needs to be done
We want users to be able to see information about failed eCRs in the dashboard so they can have the data points that they need to share with the DIBBs team for troubleshooting and support.
🏗️ Acceptance Criteria
Given an eCR is sent to the orchestration service to be saved
And the eCR Viewer is running in non-integrated mode
When a step in the pipeline fails
Then 🔮fields🔮 need to be sent to the eCR Viewer to be logged
⚙️ Technical Notes
📜 Additional context
The text was updated successfully, but these errors were encountered:
🚧 What needs to be done
The orchestration service needs to know when and where an eCR message has failed in the pipeline and send that failure with the run data to the eCR Viewer for storage
🤔 Why it needs to be done
We want users to be able to see information about failed eCRs in the dashboard so they can have the data points that they need to share with the DIBBs team for troubleshooting and support.
🏗️ Acceptance Criteria
⚙️ Technical Notes
📜 Additional context
The text was updated successfully, but these errors were encountered: