Workflow Execution from Automation Service Broker Catalog without Counting this as a Deployment

[Stefan Schnell]

Yesterday I tried to execute a workflow from the Service Broker catalog as described in the documentation, add Automation Orchestrator workflows to the Automation Service Broker catalog. All works well and as expected so far. However, each time the workflow is executed from the Service Broker, a deployment is also created automatically. This is completely independent of what the workflow actually does, even if only Hello World is output. Each of these executions is then also counted as a deployment in the projects. I now have two questions about this:

1. Is each successful deployment subtracted from the instance limits in the project? This means, for example, that if I entered 5 instances as a limit and 5 workflows have been successfully executed in this way, no more are possible?
2. Is it possible to execute an workflow on this way without increasing the counter of deployments?

Thanks for answers and hints.

Best regards
Stefan

[Victoria hubb]

Hello,

Yes, each successful deployment is subtracted from the instance limits in the project. If you set a limit of 5 instances and 5 workflows are executed, no more deployments will be possible until the limit is increased or some instances are removed.

To execute a workflow without increasing the deployment counter, you might need to adjust the workflow settings or use a different method to run the workflows. Unfortunately, the default behavior of Service Broker counts each execution as a deployment. You may want to consult the documentation or reach out to support for specific configurations that might bypass this limitation.

If you need further assistance, feel free to ask!

Best regards

Victoria hubb