Skip to main content

Overview

Event-driven pipelines execute automatically when specific platform events occur. React to model deployments, cluster changes, or custom events without manual intervention.

Available Event Types

Creating Event Triggers

In the UI

  1. Open your pipeline
  2. Go to Triggers tab
  3. Click Add Event Trigger
  4. Configure:
    • Event Type: model.added
    • Filter (optional): JSON condition
    • Enabled: Toggle on
  5. Click Save

Using the SDK

Event Filtering

Filter events to only trigger for specific conditions:

Event Data Access

Access event data in your pipeline using the event context:

Example: Auto-Deploy on Model Add

Automatically deploy models when they’re added to the registry:

Example: Failure Alert Pipeline

Send alerts when deployments fail:

Managing Event Triggers

List All Triggers

Disable a Trigger

Update Filter

Best Practices

Use Filters: Avoid triggering on every event - filter for relevance
Idempotent Actions: Ensure pipeline actions are safe to retry
Add Logging: Track which events triggered executions
Test Events: Manually trigger test events before enabling
Monitor Executions: Watch for unexpected trigger frequency

Event Data Structure

Each event includes standard fields:

Troubleshooting

Cause: Event filter too restrictive or trigger disabledSolution: Check filter conditions, verify trigger is enabled
Cause: Events firing more frequently than expectedSolution: Add more specific filters, check event source
Cause: Event payload doesn’t include expected fieldsSolution: Check event schema, add fallback values in pipeline

Next Steps

Scheduled Pipelines

Run pipelines on a schedule

Troubleshooting

Common issues and solutions