> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/creating-and-running-projects/running-projects/running-from-the-home-page.md).

# Running from the Home Page

You can run your project directly from the appRules Home Page.  Click the Run button on the Project Toolbar and the following modal will be displayed:

<div data-with-frame="true"><figure><img src="https://1923141441-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFjmFrZ8sef1J7qkr6H%2Fuploads%2FjnnpI4FKE4CA3ICaMZx5%2Fimage.png?alt=media&amp;token=f3c4a2c3-4890-4e8f-8c93-f43070e3a365" alt=""><figcaption></figcaption></figure></div>

Enter an optional reference for the job, the Server on which to run the job (or Default).  "Max Run Time" and "Cache TimeSpan" are defined in the project settings for the project.

Check whether to run the job in background and if extended logging is required (for example if you are debugging the project).

View Execution Flow: this feature allows to view the process running activity by activity (only available in design run, not in background run). The delay specifies the temporisation.

Click the Run toolbar button to run to job.

Jobs Arguments Tab: specify the argument values if defined for this workflow


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appstrategy.com/apprules-r-documentation/platform/platform-features/creating-and-running-projects/running-projects/running-from-the-home-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.