# Deployment-Aware Job Executor

**URL:** <https://forum.camunda.io/t/deployment-aware-job-executor/7572>\
**Category:** Discussion & Questions\
**Tags:** process-engine\
**Created:** [June 5, 2018, 8:55am UTC](https://forum.camunda.io/t/deployment-aware-job-executor/7572 "2018-06-05T08:55:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![thorben](https://forum.camunda.io/user_avatar/forum.camunda.io/thorben/32/78_2.png) [@thorben](https://forum.camunda.io/u/thorben)\
**Post date:** [June 5, 2018, 9:53am UTC](https://forum.camunda.io/t/deployment-aware-job-executor/7572/2 "2018-06-05T09:53:11Z")

</div>

Hi Timo,

If you run a deployment-aware job executor, then the job executor only picks up deployments that are _registered_ with the process engine.

How registration happens:

- Whenever a deployment is made via API
- Whenever a process application is (re-)deployed, it registers all deployments it makes and resumes
- Manual registration via `ManagementService#registerDeploymentForJobExecutor`
- Registrations are not persisted

So in order to answer your questions, we would have to look at when these things happen, which depends on how you deploy your processes.

Cheers,  
Thorben

---

_[View the full topic](https://forum.camunda.io/t/deployment-aware-job-executor/7572)._
