# S-Doc Job Statuses

Before attempting to troubleshoot S-Doc Job errors, we recommend navigating to the template record(s) being used with the S-Doc Job and running a [**Save & Preview**](https://www.sdocs.com/resources/documentation/developers-guide/template-preview/). If the document does not generate successfully, your issue likely has to do with the document template itself. If the document does generate successfully, move on to the troubleshooting information below.

***

{% hint style="warning" %}
For jobs stuck at **35, 40, 60, 80, or 90%** you can navigate to Setup > Apex Jobs and look for a failed Apex job. The error message on the Apex Job may provide additional information.
{% endhint %}

## S-Doc Job Status Errors

1. Completed: The documents have been created and (if relevant) emailed successfully
2. Error: The job failed. Check the *Status Details* section for more information
3. Error (Run As User Failed): The Run As User callout failed. Check the Status Details field for more information, and ensure you have configured the [**Run As User**](https://www.sdocs.com/resources/documentation/allow-s-docs-jobs-api-calls-to-be-run-as-another-user/) feature correctly
4. 10: An error occurred in transition from the job creator user to the Run As User user. Ensure you have configured the [**Run As User**](https://www.sdocs.com/resources/documentation/allow-s-docs-jobs-api-calls-to-be-run-as-another-user/) feature correctly
5. 35: An error occurred processing concurrent job splitters
6. 40: An error occurred in part 1 of document generation (aka processing Runtime Prompts)
7. 60: An error occurred in transition from part 1 of document generation to part 2 of document generation
8. 80: An error occurred in part 2 of document generation, file/attachment creation, or emailing
9. 90: The document(s) were generated successfully, but an error occurred during S-Sign processing

## Related articles

Error rendering macro 'contentbylabel' : CQL was parsed but the search manager was unable to execute the search. Error message: com.atlassian.confluence.api.service.exceptions.scale.SSStatusCodeException: There was an illegal request passed to XP-Search Aggregator API : HTTP/1.1 403 Forbidden


---

# 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://help.sdocs.com/sdocs/maintenance-and-troubleshooting/legacy-workflows/s-doc-jobs-legacy/s-doc-job-statuses.md?ask=<question>
```

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.