> For the complete documentation index, see [llms.txt](https://docs.jmapcloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jmapcloud.io/en/jmap-cloud-portal/user-guide-for-jmap-cloud-portal/jobs.md). # Jobs This section displays the jobs that your organization runs on JMap Cloud. Its purpose is to provide information about issues that may arise during the execution of certain functions. The table displays jobs as rows with the following fields as columns:

Field	Description
Type	Indicates the type of job executed by JMap Cloud: Load, Analyze, Seed, etc.
Id	Unique identifier of the job.
Status	Execution state of the job: Cancelled, Success, etc. In case of an error, a more detailed message can be viewed by clicking the icon to the right of the failed status.
Message	A brief message describing the executed job.
Progress	The degree of completion of the job, as a percentage.
Created	Job creation date.
Start	Job start date.
End	Job end date.
Updated	Job last updated date.

Members with the **Administrator** role can view all jobs in the organization. Members with the **Manager** role can view only the jobs they have started. A job can be cancelled only by the member who started it. --- # 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://docs.jmapcloud.io/en/jmap-cloud-portal/user-guide-for-jmap-cloud-portal/jobs.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.