Workflow Jobs in R-COM Gateway
Workflow Jobs are a powerful diagnostic and monitoring tool in R-COM Gateway. Every time a workflow is triggered, whether by RFID scans, API calls, MQTT messages, or custom events, it results in a workflow job. These jobs record exactly how the workflow ran: what data it processed, what actions it performed, and whether it succeeded or failed.
They are essential for:
- Operational Transparency: Understanding what your automation is doing.
- Debugging: Isolating issues when workflows fail.
- Optimization: Finding bottlenecks or inefficiencies in your logic.
Accessing Workflow Jobs
To review past executions/workflow jobs:
- Navigate to Automation > Workflow Jobs in the sidebar.
- The list initially shows jobs created today. It includes a Created filter set to today, along with job-status filters.
- To review older jobs, change or remove the Created filter. You can combine filters with Match All or Match Any, then use New view to save the result. Select Default to return to the default view.
- The table is sorted by most recent first.
- Each entry provides a snapshot of that workflow’s execution.
List of workflow jobs
Workflow Jobs Table Overview
| Column | Description |
|---|---|
| Job ID | Unique identifier for the workflow job. |
| Workflow | Name of the executed workflow. |
| Workflow Version | Version of the workflow that ran. |
| Job Tags | Tags used to categorize and filter jobs. |
| Custom Status | Business status assigned by workflow actions such as SetJobStatus. |
| Error Identifier | Custom error identifier attached during execution, when present. |
| Status | Runtime result, such as Completed or AbortedDueToFailedAction. |
| Created | Timestamp when the job started. |
| Completed Time | Timestamp when the job finished or failed. |
| Actions | Use View source event, View job logs, or View job context to investigate the execution. |
Viewing Workflow Logs
To inspect what happened in a specific job, select View job logs on the job row. The Execution logs dialog shows timestamped entries for that execution.
- Use the log-level multi-select to focus on entries such as
FINEST,WARNING, orERROR. - Select Include system logs when system-level entries are needed for troubleshooting.
- Select Download job logs to save the displayed job logs.
- Select Refresh to retrieve the latest entries for a running job.
Example Error:
List of workflow jobs
This particular error indicates that the workflow was terminated because a database entry with the same name already existed during the execution of the CreateTemporaryFile action.
Inspecting Workflow Context
To understand how variables were set and transformed during a job, select View job context on the job row. The Execution context dialog shows runtime values including:
- Global variables (
CLIENT_ID,SUBWORKFLOW_API_BASE, etc.) - Payload-specific fields (
objid,T_CUSTOMER, etc.) - and more...
Workflow context
This is particularly useful when troubleshooting value mismatches, null references, or incorrect variable propagation in complex workflows. Use the copy control beside an individual value to copy it, or select Download job context to save the complete context as JSON.
Common Status Indicators and Their Meaning
| Status | Meaning |
|---|---|
Completed | Workflow ran successfully with no errors. |
Failed | A general failure occurred, often logic or data related. |
AbortedDueToFailedAction | A required action failed, stopping execution. |
CompletedButFailureOnDBUpdates | Workflow logic ran fine, but DB/storage update failed. |
WorkflowNotFound | The referenced workflow was missing or deleted. |
Created, Started, Undefined | Intermediate or rare internal statuses. |
Use the combination of Logs + Context to trace and correct such issues.
Example Troubleshooting Flow
- Check Status →
AbortedDueToFailedAction. - Click Logs → Review the exact step that failed.
- Click Context → Confirm that variables were correctly passed.
- Update the workflow logic or fix the source data (e.g., correct SQL column name).
- Select View source event on the job row to open the related event. To retry it, go to Automation > Events, find the event, and select Rerun event.