MarkError
Mark Error Plugin – Mark
Summary (SEO Meta Description):
The Mark Error plugin in WeHub marks workflow execution as failed with a custom error message.
Useful for debugging, error handling, and stopping workflows when conditions are not met.
Overview
The Mark Error Plugin is used to explicitly fail a workflow step and record a custom error message.
It is especially useful when certain validation checks fail, when unexpected data is encountered, or when you need to halt workflow execution for safety.
This plugin ensures errors are captured intentionally rather than silently passing through.
⚙️ Action: Mark
- Description: Marks the workflow as failed and records a descriptive error message.
- Use Case: Trigger controlled workflow failure with meaningful context.
Configuration Options:
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the node (e.g., "Error: Missing Patient ID"). |
| Message | String | Custom error message explaining why the workflow failed. |
💡 Example Use Cases
- Validation Failure: Stop workflow if mandatory fields (like Patient ID) are missing.
- Custom Error Logging: Mark error with specific message for audit trails.
- Conditional Checks: Combine with Rule Engine or Conditions Plugin to fail workflows if rules are not met.
- Debugging: Intentionally throw errors during workflow testing.
FAQ
Q: Does marking an error stop the workflow?
A: Yes, the workflow is marked as failed at that point.
Q: Can I recover from a marked error?
A: Only if you design error-handling logic outside this node. Otherwise, the workflow stops.
Q: Will the error show in logs and alerts?
A: Yes, marked errors are captured in workflow logs and can trigger notifications if alerting is enabled.
Keywords: WeHub Mark Error Plugin, Mark Workflow Error, custom error handling, workflow failure, debugging plugin