# SplitEvery Considerations

Purpose

Inserting the tag allows code to be broken up and processed into chunks.

For example: The following line of code breaks up the processing into chunks of 5 records at a time.

```
<splitEvery> 5 </splitEvery>
```

Concern and Considerations

**The concern with splitEvery:**

* Cannot work within HTML tags such ,, tags.

  **Consideration when using splitEvery:**

  * The only way splitEvery works effectively is placing it on the parent level and leveraging a component template for every record queried.
  * When splitEvery is leveraged, an SD Job is supposed to be created.
  * splitEvery is typically leveraged to split jobs and stay below the APEX CPU time limit error.
* No related lists can be encapsulated in HTML tags in the parent template even if a related list using splitEvery is not encapsulated in HTML tags itself.
* Does not work properly when placed in a component template.


---

# 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/job-splitters/splitevery-considerations.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.