> For the complete documentation index, see [llms.txt](https://docs.fieldmotion.com/fieldmotion-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fieldmotion.com/fieldmotion-api-docs/job/_setstatus.md). # \_setStatus Sets the status of the Job. ### Parameters #### id The ID of the Job. #### value The new status of the Job. Set to 0 for Not Complete, 1 for Complete and 2 for Processed. ### Example ``` FM_api('Job_setStatus', ['id' => '123', 'value' => '1']); ``` ### Result #### On Success ``` {'ok':1} ``` #### On Failure If the Job ID is not given: ``` {'error':'no ID supplied'} ``` If the status is not given: ``` {'error':'no value supplied'} ``` If the Job is not found: ``` {'error':'appointment does not exist'} ``` If the status is changed to Processed when the Job is not completed: ``` {'error':'This status update cannot be done until the appointment is completed'} ``` --- # 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.fieldmotion.com/fieldmotion-api-docs/job/_setstatus.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.