# 27 September: Sequence Enhancement

### Sequence: Step Log and Reporting Improvement 

\
We’ve upgraded the Sequence Logs experience to make monitoring and debugging much easier.

How to Access:\
Go to Sequence → Select a Sequence Name → Logs

What’s New:

* Step numbers are now displayed in execution order for better clarity.
* The label “Step Name” has been updated to “Template Name.”
* Sent date/time is now shown in a more user-friendly format.
* Error reasons are displayed for failed or queued steps.
* The View Conversation tab is now easier to access.
* The Logs Home Page includes a new Error component and improved filter order.

These enhancements help users quickly identify issues, review message flow, and manage sequences more efficiently.

<p align="center"><img src="file:///C:/Users/DIPAKG~1/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png" alt=""><img src="/files/Sz48au2fzcRyGTdWQF7h" alt="z9gO8gAAAAGSURBVAMAloEduYNvw5UAAAAASUVORK5CYII="><br><br></p>

### &#x20;Sequence Enhancement: Drop on Message Failure

We’ve added a “Continue on Success” option to improve sequence control when messages fail.

Key Details:

* By default, sequences continue even if a message fails.
* If “Continue on Success” is enabled, the sequence stops at the first failed message.
* The contact is moved to a Dropped state with a “Message Failed to Send” indicator.
* Clicking on the contact opens the Step Log, highlighting the failed step for easier troubleshooting.

This feature gives users more control over message sequences and helps quickly identify issues.<br>

<p align="center"><img src="/files/agHq8bita1V62Hzg2dDY" alt="C9F73jQAAAAASUVORK5CYII=" data-size="original"></p>

<p align="center"><img src="file:///C:/Users/DIPAKG~1/AppData/Local/Temp/msohtmlclip1/01/clip_image008.png" alt=""><br><img src="/files/6fPVWnm0GQNXs8tJghPN" alt="+UFHVoAAAABklEQVQDAN7pWp0YMBTMAAAAAElFTkSuQmCC"> </p>

### &#x20;Sequence Enhancement: Improved Error Handling

We’ve optimized how sequences handle specific error cases to improve accuracy and reporting.

Key Details:

* Contacts with Error 131026 (Not in WhatsApp) are now moved to Dropped with the reason “Contact Not in WhatsApp.”
* Contacts with Error 131050 (Opted Out) are marked as Dropped, and the Marketing Opt-In field is automatically updated to No.

These updates ensure clearer tracking of failed messages and maintain accurate contact status for marketing compliance.

&#x20;

Sequences now automatically remove contacts who cannot receive messages, ensuring smoother execution and cleaner contact lists.

Key Details:

* Contacts not reachable via WhatsApp or who have opted out are moved to Dropped automatically.
* This prevents further sequence steps from attempting delivery and keeps sequence logs accurate.<br>

<p align="center"><img src="/files/VUH9J01qEhnxxeBGMUkY" alt="2wetc8AAAAGSURBVAMAlVrBoS7npO8AAAAASUVORK5CYII="> </p>

&#x20;

<p align="center"><img src="file:///C:/Users/DIPAKG~1/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png" alt=""><img src="/files/TKDlHSww0rwo54mPlG4q" alt="+XqJU5AAAABklEQVQDAEEf0o9MuYlXAAAAAElFTkSuQmCC">      </p>

&#x20;


---

# 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://changelog.gallabox.com/september-2025/27-september-sequence-enhancement.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.