# Step 4: Store the Skipped Customer record

Once all the skipped customer records are stored in the list, and the ETL pipeline has been executed, the “On Completed” function is executed. 

This exercise defines actions in the “On Completed” function to store the deleted records details in a target entity.

* To define the Actions to be executed once the ETL pipeline run is completed, go to the Code tab>On Completed function. \
  To define the actions, add an “Action box” by clicking the \[+ Action box] button.

<figure><img src="https://media.langstack.com/documentation/media/images/code/training_manual/chapter_9/ch9ex1st4ocaddactbox.png" alt=""><figcaption></figcaption></figure>

* To traverse the list of skipped records, add and define the following action in the “Code” tab:
  1. Select Action as “Traverse List”.&#x20;
  2. Select Target Value as “skippedRecordsList”.&#x20;
  3. The Variable “item” is created.

<figure><img src="https://media.langstack.com/documentation/media/images/code/training_manual/chapter_9/ch9ex1st4octraverselist1.png" alt=""><figcaption></figcaption></figure>

* To create the entity record for the skipped records detail from the traversed item, add and define an action in the Traverse List action as follows:&#x20;

  1. Select Action as “Create Entity record”.&#x20;
  2. Create the JXPResponse variable “Result” by clicking the \[+] button.&#x20;
  3. The Entity variable “item” is created.
  4.

  ```
  <figure><img src="https://media.langstack.com/documentation/media/images/code/training_manual/chapter_9/ch9ex1st4occreateentityrec.png" alt=""><figcaption></figcaption></figure>
  ```
* To save the ETL pipeline, click \[Save].

<figure><img src="https://media.langstack.com/documentation/media/images/code/training_manual/chapter_9/ch9etlsave.png" alt=""><figcaption></figcaption></figure>

* To publish the ETL pipeline, click \[Publish].

<figure><img src="https://media.langstack.com/documentation/media/images/code/training_manual/chapter_9/ch9publishetl.png" alt=""><figcaption></figcaption></figure>

* Ensure the ETL pipeline is enabled.

<figure><img src="https://media.langstack.com/documentation/media/images/code/training_manual/chapter_9/ch9enableetl.png" alt=""><figcaption></figcaption></figure>

* Click the \[Run] button.

<figure><img src="https://media.langstack.com/documentation/media/images/code/training_manual/chapter_9/ch9runetl.png" alt=""><figcaption></figcaption></figure>

* The Run ETL pipeline dialog box displays. \
  To add a parameter (to add value for StartupParameters) click the \[+ Parameter] button. \
  Add three (3) parameters.

<figure><img src="https://media.langstack.com/documentation/media/images/code/training_manual/chapter_9/ch9runaddparameter.png" alt=""><figcaption></figcaption></figure>

* To skip records with Customer\_ID as “3”, “5”, and “7”, enter the StartupParameters as per the image below. \
  These values will be traversed to match with the Customer\_ID to skip creating relevant records. \
  To run the ETL pipeline, click the \[Run] button.

<figure><img src="https://media.langstack.com/documentation/media/images/code/training_manual/chapter_9/ch9runaddparam357.png" alt=""><figcaption></figcaption></figure>

* For a list of Customer IDs ranging between 1 and 17 (odd numbers), the records with Customer\_D “3”, “5”, and “7” are skipped in the target destination.

<figure><img src="https://media.langstack.com/documentation/media/images/code/training_manual/chapter_9/ch9skiprecentity.png" alt=""><figcaption></figcaption></figure>


---

# 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://docs.langstack.com/welcome/get-started/learn-langstack/introduction-to-etl-pipeline/exercise-1-skip-customer-records/step-4-store-the-skipped-customer-record.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.