Deployment Targets & Runtimes
What considerations apply when running Catalyst agent workflows as long-running services?
Running Catalyst agent workflows as long-running services is a viable deployment option. Since Catalyst is built on Dapr, you can deploy agent workflows as persistent services without rewriting code, retaining execution context across routine updates and restarts. Network data transfers only occur when the agent interacts with external tools or datastores. Ensure the underlying host environment does not enforce resource limits that disrupt long-running workflow loops.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Deployment Targets & Runtimes
Can I run Catalyst agent workflows on standard FaaS platforms?
This guide outlines critical compatibility and operational constraints for deploying Catalyst agent workflows on standard FaaS platforms for production use
- Deployment Targets & Runtimes
Can I deploy Catalyst agent workflows on self-managed Kubernetes clusters?
This resource details critical compatibility and setup considerations for running Catalyst agent workflows on self-managed Kubernetes clusters
- Deployment Targets & Runtimes
Can I deploy Catalyst agent workflows to managed container services?
This overview covers key compatibility and operational notes for deploying Catalyst agent workflows on managed container services
