> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/articles-1/get-started/core-concepts/entities-overview.md). # Entities Overview ## Job You create a job that includes configurations such as schema handling and the SQL transformations to perform on the data. Jobs are always active until you delete them. Furthermore, a job is not a time entity. ## Execution / Run An instance of a job at a specific point in time. An execution/run includes the job definition (transformations and so on), execution start time, and execution/run end time. ## Stage An execution is divided into multiple logical stages. A stage consists of many different tasks or units of work. A stage is complete when all tasks associated with that stage are complete. It does not have a time associated with it. For example, in an ingestion job, a COPY operation can be a single stage associated with many tasks. ## Task A task represents the actual unit of work executed. An execution can have multiple stages and multiple tasks per stage. A task always belongs to one stage. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://upsolver.gitbook.io/content/articles-1/get-started/core-concepts/entities-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.