# Resource Allocation During run-time recipes can be executed by a BPMS which leades to a optimized resource allocation.\ Rembrandt allows two ways of starting the allocation: * Calling the corresponding API route. * Clicking the button in the recipe detail view. The GET request to start the allocation can be called from an arbitrary BPMS at any time. \ If Rembrandt is used locally with the standard port, the request looks like this: ``` localhost:8080/optimization/[recipeId]/execute ``` ### Executions Started executions can be seen in the frontend within the "Executions" page in the optimization component.\ In the detail view of a specific execution ingredients and their current state are displayed, which enables better monitoring and debugging of the resource allocation process.\ If an execution is no longer relevant, it can be **deleted** to maintain clarity. This, however, does not stop the allocation process in the backend, but only deletes the visible front end records. ![](/files/-LmoRtNLXvU6avonEqbj) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://rembrandt.gitbook.io/docs/user-guide-1/resource-allocation.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.