Skip to main content
Monitor workflow execution with detailed logs, performance metrics, and debugging tools to ensure reliable automation operation.

​
Understanding workflow runs

A workflow run represents a single execution triggered by an event and tracked from start to completion.

Run states

Runs progress through distinct states during execution:Pending: Waiting for execution resourcesRunning: Actively processing workflow stepsCompleted: All steps finished successfullyFailed: One or more steps encountered errorsCancelled: Execution stopped manually or by system
Each run captures comprehensive information:
  • Start time and duration
  • Trigger context and inputs
  • Step-by-step execution results
  • Success and failure counts
  • Error messages and stack traces
Access workflow run history from the workflow detail page:
  • Filter by status (completed, failed, running)
  • Search by trigger data or time range
  • Sort by execution time or duration
  • Export logs for analysis

​
Step-by-step logging

Each workflow step is individually tracked with detailed execution information.
View comprehensive step information:
  • Input values (raw and resolved)
  • Output data produced
  • Execution duration
  • Error messages if failed
  • Dynamic value resolution
See how data flows through your workflow:
  • Trigger data passed to actions
  • Action outputs used by subsequent steps
  • Dynamic reference resolution
  • Value transformations applied
Example: View how ticket priority from trigger determines Slack channel in notification action
Understand execution flow with timeline view:
  • Sequential step execution order
  • Parallel action execution
  • Wait times between steps
  • Total workflow duration

​
Performance monitoring

Track workflow performance with detailed metrics and dashboards.

Execution metrics

Monitor executions per day, average duration, and peak usage periods

Success rates

Track completion rates and identify reliability trends

Error frequency

Monitor error patterns and failure rates over time

Resource usage

View processing times and identify performance bottlenecks
Performance data helps with capacity planning by showing when workflows are most active and how long operations take.

​
Debugging workflows

Systematic approach to identifying and resolving workflow issues.
1

Review error messages

Check execution logs for specific error details and context
2

Examine execution timeline

Identify which step failed and review its inputs
3

Check step outputs

Verify data flowing between steps matches expectations
4

Test dynamic references

Ensure dynamic values resolve correctly with test data
5

Verify integrations

Confirm external services are available and authenticated
6

Isolate the issue

Test individual steps when possible to narrow down problems
7

Fix and retest

Make corrections in draft mode and test before republishing

​
Common issues

Possible causes:
  • Workflow is in draft state (not published)
  • Trigger filters don’t match the event
  • Workflow is disabled
  • Integration disconnected
Solution:
  • Verify workflow is published and active
  • Review trigger configuration and filters
  • Check workflow settings for disabled state
  • Reconnect any disconnected integrations
Possible causes:
  • Missing required fields
  • Invalid dynamic references
  • Permission issues
  • External service unavailable
Solution:
  • Check runs and logs for error details
  • Verify all required fields are populated
  • Test dynamic references with manual run
  • Confirm integration permissions are correct
  • Verify external service is operational
Possible causes:
  • Wrong dynamic reference selected
  • Data transformation issue
  • Trigger data missing expected fields
Solution:
  • Review dynamic value configuration
  • Check trigger data structure in logs
  • Verify field names match exactly
  • Test with manual trigger using known data
Possible causes:
  • External API delays
  • Complex conditional logic
  • Multiple sequential actions
  • Large data volumes
Solution:
  • Consider parallelizing actions where possible
  • Simplify conditional logic
  • Use async actions when available
  • Review external service performance
Possible causes:
  • Disconnected integration
  • Expired credentials
  • Insufficient API permissions
  • Rate limiting
Solution:
  • Reconnect integration from settings
  • Refresh authentication credentials
  • Verify required API scopes are granted
  • Check rate limit status in integration logs

​
Error types

Understanding error categories helps diagnose issues quickly.
Invalid input data or configuration:
  • Missing required fields
  • Invalid field formats
  • Out of range values
  • Type mismatches
Fix: Review field requirements and provide valid data
External service failures:
  • Connection timeouts
  • Authentication failures
  • API rate limits
  • Service unavailable
Fix: Check integration status and external service health
Insufficient access rights:
  • Missing API scopes
  • User lacks required permissions
  • Channel or resource access denied
Fix: Grant necessary permissions in integration settings
Steps taking too long to execute:
  • External API delays
  • Large data processing
  • Network issues
Fix: Optimize workflow or increase timeout settings

​
Workflow attribution in tickets

Track which workflows triggered automated changes in tickets. Each ticket event shows the workflow and run details that caused the update.
Ticket event logs display:
  • Workflow name that made the change
  • Run ID for the specific execution
  • Timestamp of the update
  • Changed field values
Trace any automated update back to its source workflow and examine the specific run that caused the change.
Use workflow attribution for:
  • Debugging unexpected ticket changes
  • Understanding automation impact
  • Compliance and audit requirements
  • Team accountability for automated processes

​
Log management

Workflow logs are retained for analysis and compliance:
  • Run logs: Standard retention period
  • Error logs: Extended retention for analysis
  • Performance metrics: Long-term trending data
Export logs before retention period expires if needed for long-term storage.
Log access is controlled by user permissions:
  • View logs for workflows you own or manage
  • Workspace administrators see all workflow logs
  • Audit trails track who accessed logs
Generate reports and export data:
  • Export execution logs for analysis
  • Create performance reports
  • Generate audit trails for compliance
  • Download error logs for troubleshooting

​
Failure notifications

Configure notifications to receive alerts when workflow runs fail through email or Slack, ensuring prompt awareness of automation issues.

Email alerts

Subscribe to email notifications for workflows you manage to receive personal failure alerts

Slack channels

Configure Slack channels to notify entire teams when critical workflows fail

​
Configuring failure notifications

Set up failure notifications from the workflow Settings tab to control how and where your team receives alerts.
1

Open workflow settings

Navigate to your workflow and select the Settings tab
2

Configure email notifications

Toggle Email me on failures to receive personal email alerts when the workflow fails
3

Configure Slack notifications

Connect a Slack channel to post team notifications when workflow runs fail
4

Test notifications

Trigger a test failure to verify notifications are delivered correctly

​
Email notifications

Personal email alerts notify you immediately when workflows you manage encounter failures. Features:
  • Individual subscription per workflow
  • Includes workflow name, run ID, and direct link to failure details
  • One-click unsubscribe without requiring authentication
  • Branded email template matching your organization
Use email notifications when:
  • You need personal alerts for critical workflows
  • You want offline notification access
  • You manage workflows requiring immediate attention
  • You prefer email over Slack for failure tracking

​
Slack notifications

Team Slack notifications post failure alerts to channels where your team collaborates, enabling quick response and coordination. Features:
  • Configure one Slack channel per workflow
  • Block Kit formatted messages with clickable buttons
  • Direct link to view run details in Ravenna
  • Posts to any Slack channel in connected workspaces
Use Slack notifications when:
  • Teams need collective awareness of failures
  • Failures require coordinated response
  • You want failures visible in team communication channels
  • Multiple people share responsibility for workflow reliability
Email and Slack notifications work independently. You can enable both to ensure critical workflow failures reach your team through multiple channels.

​
Unsubscribing from emails

Workflow failure emails include a one-click unsubscribe link that requires no authentication.
1

Click unsubscribe link

Open the failure notification email and click the unsubscribe link at the bottom
2

Confirm unsubscribe

You’ll see a confirmation message that you’ve been unsubscribed
3

Resubscribe if needed

To resubscribe, visit the workflow Settings tab and toggle email notifications back on
Unsubscribe links are unique to each user and workflow. Clicking an unsubscribe link only affects your notifications for that specific workflow.

​
Best practices

Configure email and Slack notifications for workflow failures from the Settings tab. Personal email alerts keep you informed while Slack channels enable team coordination when critical automations encounter issues.
Schedule periodic reviews of workflow performance and error rates. Look for patterns like increasing failures or performance degradation.
Keep notes on resolved issues and their solutions. This helps troubleshoot similar problems faster in the future.
Always test workflows after making updates. Monitor first few executions closely to catch any issues early.
Regularly verify integration health and refresh credentials before they expire. Update API permissions when integrations add new features.