📄️ Passing Inputs to Tasks in Conductor
When you start a Conductor workflow, you can pass inputs to the workflow - which can be used as parameters for various steps in the workflow. As the tasks progress in a workflow - each task will create its own outputs. So how can this data from previous tasks be used in the steps succeeding it? In Conductor, data can be passed to a task in different ways, such as from workflow inputs/outputs, prior task inputs/outputs, variables, and secrets.
📄️ Unit and Regression Testing Workflows
📄️ Integration with CI/CD
Conductor workflows are the core part of your application and should be versioned, controlled, and released similarly to the code.
📄️ Scheduling Workflows
Often we want to trigger a workflow at a specific schedule. Orkes Conductor platform supports this natively. The workflows can be configured to be triggered at any cadence as required using the crontab expression.
📄️ Webhook Integration
Webhooks are user-driven HTTP callback functions that facilitate the connection between Orkes Conductor and other third-party systems. Webhook sends data from one system to another when an event occurs. By leveraging Webhooks, workflows can be built to act on events outside the Conductor environment. You can also trigger other workflows in Conductor based on the received Webhook events.
📄️ Write Workflows Using Code
Workflows can be written in code, allowing the creation of dynamic workflows that can't be pre-defined. Support for defining workflows using code is part of all the supported SDKs.
📄️ Human Task
Human tasks are used when you need to pause your workflow for an interaction from a human. When your workflow reaches the human task, it waits for a manual interaction to proceed with the workflow.
📄️ Debugging Workflows
Orkes Conductor provides a visual representation of workflows that aids in quickly troubleshooting issues. Conductor UI provides us with the ability to look into workflow executions which helps in quickly spotting and resolving issues.
📄️ Routing Tasks (Task to Domain)
Typically, for each configured task type - Conductor server will maintain a queue and will distribute task work to all the
📄️ Using Secrets in Conductor
Often times we have requirements where sensitive values are used in workflows. In such situations, secrets can be
📄️ Guide to Scaling Workers
Workers are responsible for executing business logic in the workflow applications. Scaling and performance tuning workers are dependent on the following metrics:
📄️ Orkes Conductor Dashboard - Metrics & Observability
The Orkes Conductor Dashboard gives a quick overview of the metrics & alerts on your Conductor console. It provides a centralized intuitive interface to track and get insights on the behavior and performance of tasks and workflows that can aid in troubleshooting errors.
📄️ Monitoring Task Queues
The task queues are the collection of tasks waiting to be executed. It is useful for viewing the details, such as the number of workers polling and monitoring the queue backlog.
📄️ Workflow Versions at Runtime
The Conductor workflow can be versioned, which means you can have multiple versions of the same workflow.
📄️ Task and Workflow Status in Conductor
The status of the task and workflow is crucial while debugging a workflow from UI. You can look into the workflow and task status to understand the current state of the workflow to identify any potential issues or errors.
📄️ Sending Signals to Workflows
In certain scenarios, there might arise a need to transmit signals to workflows for purposes such as pausing, terminating, or restarting them. There are different ways through which you can achieve this.
📄️ Event Streaming with Azure Event Hub
Streamlining the monitoring and management of tasks and workflows is vital in orchestration. With Orkes Conductor, you can publish and consume task and workflow status change stream events by integrating with the powerful event streaming platform Azure Event Hub.