📄️ General FAQs
Is it possible to pull data from multiple endpoints simultaneously rather than sequentially?
📄️ How do we monitor log levels in Conductor?
Conductor is based on Spring Boot, so the log levels are set via Spring Boot properties.
📄️ How can we reuse tasks?
A powerful feature of Conductor is that it supports and enables re-usability out of the box. Task workers typically perform a unit of work and are usually a part of a larger workflow. Such workers are often reusable in multiple workflows. Once a task is defined, you can reuse it multiple times in the same workflow (with a different TaskReferenceName). Once defined, tasks can also be used in multiple workflows.
📄️ Are Conductor Workflows Directed Acyclic Graph (DAG)?
Conductor workflows are directed acyclic graphs (DAGs). But what exactly is a DAG?
📄️ What is Workflow Versioning in Conductor?
Workflow versioning is the ability to manage different versions of a workflow. This feature allows you to make changes to a workflow without affecting the existing version of the workflow that is already running or scheduled to run.
📄️ What is Task lifecycle?
Task state transitions
📄️ How to connect to Azure Service Bus?
The following property needs to be set in your cluster's Conductor Server.
📄️ How are task outputs cached in Conductor?
Certain task types support the task caching functionality, where you can enable the "Cache output" option that allows saving of task outputs for future use. On enabling this option, you need to provide the following parameters: