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
@@ -711,7 +711,7 @@ Conditional evaluators are logical statement strings that may be used to determi
711
711
712
712
NOT_CONTAINS (Valid for integers and strings compared to lists)
713
713
714
-
more information on conditionals can be found [Conditionals Docs](guidelines\mwm-conditionals.md)
714
+
more information on conditionals can be found [Conditionals Docs](..\..\guidelines\mwm-conditionals.md)
715
715
716
716
### Context
717
717
The workflow metadata is any data that can be used by Evaluators. This includes metadata added by previous tasks, but can also include metadata about the input files (most notably DICOM tags).
@@ -799,6 +799,33 @@ An example format of the metadata.json can be found below:
799
799
800
800
execution stats are populated from the argo execution values returned automatically.
801
801
802
+
#### Handled Exception Metadata
803
+
Application models can throw handled exceptions, to do this your application model should output the properties "exception" and "exception_message" to the `metadata.json`
804
+
805
+
Example...
806
+
```json
807
+
{
808
+
"exception": "NoDicomFilesException",
809
+
"exception_message": "No dicom files found."
810
+
}
811
+
```
812
+
813
+
We recommend your application exits execution once the metadata.json has been written.
814
+
815
+
This exception can be used in the workflow task destinations queries for example like the following examples...
0 commit comments