> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wavecx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bug Fixes

> Resolved issues and bugs, so things work the way they're supposed to.

## 3.42.2

### Bugs Fixed

| What changes | Affected Area | Impact on past reports |
| :- | :- | :- |
| Views, unique visitors, clicks, scroll activity, time on Page, bounce rate, and the Embedded Demos card. | Pages | Views, unique visitors, clicks, and scroll activity are recalculated. Bounce rate is available from this release onward. |
| Step activity, referrers, and time measurements. | Demos | Corrections apply to past dates. |
| Starts, submissions, unique visitors, abandonment, completion, and average completion time. | Forms | Corrections apply to past dates. |
| New events count once. View and click counts are no longer inflated by repeats, and drop-off no longer shows exits that didn't happen. | Featurettes | Reports for the affected period can still include duplicates. |
| Android and iPad detection, event timestamps, and the “activity starting” banner. | Devices and dates | Earlier device labels and event timestamps retain their original values. The banner reflects when WaveCX first received activity. |
| Reports load using the selected date range. | Report reliability | Applies whenever you run a report. |

***

## 3.42.1

### Bugs Fixed

<table>
  <colgroup>
    <col width="285" />

    <col width="131" />

    <col width="275" />
  </colgroup>

  <thead>
    <tr>
      <th>Issue</th>
      <th>Affected Area</th>
      <th>Resolution</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>The gap between the Step X/Y progress bar and the step list was uneven. On later steps of a feature, where the feature title is hidden, the list sat almost against the progress bar.</td>
      <td>Demos - Timeline Player</td>
      <td>The spacing above the step list is now the same on every step. Mobile is unchanged.</td>
    </tr>
  </tbody>
</table>

***

## 3.42.0

### Bugs Fixed

<table>
  <colgroup>
    <col width="285" />

    <col width="131" />

    <col width="275" />
  </colgroup>

  <thead>
    <tr>
      <th>Issue</th>
      <th>Affected Area</th>
      <th>Resolution</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>When an Editor saved changes to a Live Page. those changes would turn the Page Not Live.</td>
      <td>Pages</td>
      <td>Editors can now save content changes without affecting Live status. Only Admins, or users with the Live permission, can turn content Live or Not Live.</td>
    </tr>

    <tr>
      <td>Editors could set Live status without the Live permission either by creating a new Featurette or by working outside the admin screens.</td>
      <td>Featurettes, Demos, Forms</td>
      <td>The Live permission is now enforced for all content types. Featurettes an Editor creates start as Not Live.</td>
    </tr>

    <tr>
      <td>An Editor who duplicated a Live Featurette got an error and no copy was created.</td>
      <td>Featurettes</td>
      <td>Editors can duplicate Live Featurettes. Duplicates always start as Not Live, and an Admin can turn the copy Live when its ready.</td>
    </tr>

    <tr>
      <td>Turning Device off on a 3D Demo continued to show the 3D model.</td>
      <td>Demos</td>
      <td>A 3D Demo with device off now shows the flat 2D screen, behavior is now consistent with 2D Demos.</td>
    </tr>

    <tr>
      <td>Oh phone-width screens, Demos with Device off showed no Demo screen.</td>
      <td>Demos</td>
      <td>Device-off Demos now show their screen on phones, and the feedback page has no leftover blank area.</td>
    </tr>

    <tr>
      <td>The layout preview always showed a generic illustration, no matter the device the Demo targeted.</td>
      <td>Demos\
      (Layouts)</td>
      <td>The preview now reflects the Demo's device. \
      *See Improvements page*</td>
    </tr>

    <tr>
      <td>The condensed layout's device box disappeared for mobile Demos, and the Features Nav and step cards were misplaced in the desktop preview</td>
      <td>Demos\
      (Layouts)</td>
      <td>Placement and rendering are corrected.</td>
    </tr>

    <tr>
      <td>Layout option icons showed black instead of the the selected color.</td>
      <td>Demos\
      (Layouts)</td>
      <td>Icons now show the selected color when an option is chosen.</td>
    </tr>
  </tbody>
</table>

***

## 3.41.1

### Bugs Fixed

<table>
  <colgroup>
    <col width="285" />

    <col width="131" />

    <col width="275" />
  </colgroup>

  <thead>
    <tr>
      <th>Issue</th>
      <th>Affected Area</th>
      <th>Resolution</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>Page content performance in Analytics could fail to load, including when an audience filter was set.</td>
      <td>Analytics</td>
      <td>Page content performance now loads for the selected date range, with or without an audience filter. Very long date ranges can still be too large to load for large organizations, so choose a shorter range if you see an error.</td>
    </tr>

    <tr>
      <td>Uploaded files with `#`, `?`, `%`, or `+` in the file name had a broken link or didn't display.</td>
      <td>Media Library</td>
      <td>Files with these characters now display correctly, including files uploaded before this release. Links already pasted into your content or search results may need to be updated.</td>
    </tr>
  </tbody>
</table>

***

## 3.41.0

### Bugs Fixed

<table>
  <colgroup>
    <col width="285" />

    <col width="131" />

    <col width="275" />
  </colgroup>

  <thead>
    <tr>
      <th>Issue</th>
      <th>Affected Area</th>
      <th>Resolution</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>Creating a new Tour asked for the Tour name again, getting the user stuck in a loop.</td>
      <td>Journey Builder</td>
      <td>The name prompt only appears once. After you name the Tour and pick a screen, the editor opens with that screen as the first step.</td>
    </tr>

    <tr>
      <td>Unpublishing content could report the wrong version as the one taken offline</td>
      <td>Content Versioning</td>
      <td>Unpublish now reports the version that was one taken offline.</td>
    </tr>
  </tbody>
</table>

***

## 3.40.0

### Bugs Fixed

<table>
  <colgroup>
    <col width="285" />

    <col width="131" />

    <col width="275" />
  </colgroup>

  <thead>
    <tr>
      <th>Issue</th>
      <th>Affected Area</th>
      <th>Resolution</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>Some analytics events were dropped between Oct 4-9 during periods of high traffic.</td>
      <td>Analytics</td>
      <td>Event processing now handles high-traffic periods reliably, so events are no longer lost.</td>
    </tr>
  </tbody>
</table>

***

## 3.39.0

### Bugs Fixed

<table>
  <colgroup>
    <col width="285" />

    <col width="131" />

    <col width="275" />
  </colgroup>

  <thead>
    <tr>
      <th>Issue</th>
      <th>Affected Area</th>
      <th>Resolution</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>Feedback questions could occasionally display out of order</td>
      <td>Demos</td>
      <td>Fixed — questions are now returned in the order you arranged them, every time.</td>
    </tr>
  </tbody>
</table>

***

## 3.38.0

### Bugs Fixed

<table>
  <colgroup>
    <col width="285" />

    <col width="131" />

    <col width="275" />
  </colgroup>

  <thead>
    <tr>
      <th>Issue</th>
      <th>Affected Area</th>
      <th>Resolution</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>Messages and Callouts pages could unexpectedly show a "Something went wrong" error.</td>
      <td>Messages & Callouts</td>
      <td>Fixed a shared caching issue that could load the wrong data; both pages now load correctly.</td>
    </tr>

    <tr>
      <td>Updated content could continue showing an outdated version for certain organizations.</td>
      <td>Content Delivery</td>
      <td>Fixed a cache-clearing issue affecting certain organization configurations; updates now apply as expected.</td>
    </tr>

    <tr>
      <td>Message schedules didn't start or stop on the dates set.</td>
      <td>Journey Builder — Message Scheduling</td>
      <td>Start and end dates are now properly saved and enforced, so scheduled messages show only during their intended window.</td>
    </tr>

    <tr>
      <td>Adding large groups of users to a segment could time out.</td>
      <td>Journey Builder — Segments</td>
      <td>Large segment uploads are now processed in batches, making bulk additions faster and more reliable.</td>
    </tr>
  </tbody>
</table>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.