# Task to execute at Start **URL:** \ **Category:** Developer Tools\ **Created:** [May 10, 2007, 12:21am UTC](https://tech-community.robotics.abb.com/t/task-to-execute-at-start/1195 "2007-05-10T00:21:32Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kegley182](https://avatars.discourse-cdn.com/v4/letter/k/45deac/32.png) [@kegley182](https://tech-community.robotics.abb.com/u/kegley182)\ **Post date:** [May 10, 2007, 12:21am UTC](https://tech-community.robotics.abb.com/t/task-to-execute-at-start/1195/1 "2007-05-10T00:21:32Z")
Anyone know how to get the current setting of “Task to execute at Start”? I can get the “ActiveMechanicalUnit”… but that only relates to the mech unit that will be jogged. I would like to know in my application which task(s) will be executed if the operator presses the start button. The “Task(s) to execute at start” is selected by the operator… how do I determine the setting from my app?.. or even… How do I set it from my app? 2 robot multimove system RAB 5.08… ---
**Author:** ![RussD](https://avatars.discourse-cdn.com/v4/letter/r/dec6dc/32.png) [@RussD](https://tech-community.robotics.abb.com/u/RussD)\ **Post date:** [May 10, 2007, 10:00pm UTC](https://tech-community.robotics.abb.com/t/task-to-execute-at-start/1195/2 "2007-05-10T22:00:20Z")
–update– On closer inspection this information primarily refers to whether or not the task is executable or not, as ready actually means not executable as is. If everything is OK, you will pretty much be started or stopped. –end update– The short answer is that it does not appear to be publicly exposed functionality, at least the ability to change tasks. I’m guessing that it might be this way because of the potential for unexpected motion to occur without explicit operator intervention. In 5.09, there will be a new event that you can subscribe to on a per task basis called ExecutionStateChanged, which will notify you when you enter each different state, as described below. Maybe you can use this event to get the information you need. | **Ready** | The task has no program pointer or execution context. | | --- | --- | | **Stopped** | The task has a program pointer and an execution context. | | **Started** | The task is executing. | | **Uninitialized** | The program server is not initialized. This state only exists during startup. | ---
**Author:** ![Ingela](https://avatars.discourse-cdn.com/v4/letter/i/53a042/32.png) [@Ingela](https://tech-community.robotics.abb.com/u/Ingela)\ **Post date:** [June 1, 2007, 4:18pm UTC](https://tech-community.robotics.abb.com/t/task-to-execute-at-start/1195/3 "2007-06-01T16:18:27Z")
Hello Currently the _TasksToExecuteAtStart_ setting is not exposed via the FP SDK. To READ the setting is in the plan to be included in a future release.