# 408 Error - 0.39 Story Segments

**URL:** <https://community.puzzlequest3.com/t/408-error-0-39-story-segments/1918>\
**Category:** Early Access Bug Reports\
**Created:** [December 16, 2021, 8:15pm UTC](https://community.puzzlequest3.com/t/408-error-0-39-story-segments/1918 "2021-12-16T20:15:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lyrian](https://sea1.discourse-cdn.com/flex019/user_avatar/community.puzzlequest3.com/lyrian/32/17_2.png) [@Lyrian](https://community.puzzlequest3.com/u/Lyrian)\
**Post date:** [December 16, 2021, 8:15pm UTC](https://community.puzzlequest3.com/t/408-error-0-39-story-segments/1918/1 "2021-12-16T20:15:10Z")

</div>

**Platform, device and operation system**  
Android 11, Samsung Galaxy Note 20 Ultra

**What were you expecting to happen, and what actually happened**

Expected: To start a new Story segment  
Actual: Occasional, infrequent soft locks and error messages.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/puzzlequest3/original/2X/a/a492934eb95c8514b379b9d2edaa537d8f634f4d.jpeg)

**How often does this happen? When did it begin happening?**  
_Is this a once-off issue or has it been a consistent issue? Does it only happen in specific circumstances?_

Occasionally occurs. When it happens, the error message appears on the player’s home screen. Issue may be an interim affect of the Story mode changes in 0.39.

**Steps to make it happen again**  
_Please detail the steps taken to trigger this bug. The more detailed the breakdown, the easier it is for us to test in-house._

- Play through multiple story segments (for me, I tested Chapters 3 and 4. Had one error occurrence for each Chapter.)

- Possible error more likely to occur either after many Story segments are played consecutively or after very long individual story segments (such as in Chapter 3).

---

<div class="post-metadata">

**Author:** ![PowerPlay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.puzzlequest3.com/powerplay/32/96_2.png) [@PowerPlay](https://community.puzzlequest3.com/u/PowerPlay)\
**Post date:** [December 17, 2021, 12:20am UTC](https://community.puzzlequest3.com/t/408-error-0-39-story-segments/1918/2 "2021-12-17T00:20:05Z")

</div>

That’s when you just play Skirmishes for a while; god knows you’ll need to up your gearscore anyways. It’ll be fixed soon since it directly impacts player progression.

I hope.

---

<div class="post-metadata">

**Author:** ![OminousGMan](https://sea1.discourse-cdn.com/flex019/user_avatar/community.puzzlequest3.com/ominousgman/32/915_2.png) [@OminousGMan](https://community.puzzlequest3.com/u/OminousGMan)\
**Post date:** [December 23, 2021, 5:25am UTC](https://community.puzzlequest3.com/t/408-error-0-39-story-segments/1918/3 "2021-12-23T05:25:37Z")

</div>

Hey hey!

I’ve looked into this and see that we didn’t have any server issue on the day you posted this. I do know we had some problems with the server a few days before and that there has also been issue Amazon Web Services this month, which might be linked.

Is this the first time this has happened to you? If so when did it start?

If this continues please let us know, hopefully this will resolve itself like most connection issues do.

OminousGMan - Support Human 🕵️‍♂️

---

<div class="post-metadata">

**Author:** ![Lyrian](https://sea1.discourse-cdn.com/flex019/user_avatar/community.puzzlequest3.com/lyrian/32/17_2.png) [@Lyrian](https://community.puzzlequest3.com/u/Lyrian)\
**Post date:** [December 24, 2021, 9:20pm UTC](https://community.puzzlequest3.com/t/408-error-0-39-story-segments/1918/4 "2021-12-24T21:20:16Z")

</div>

Heya, Gman.

> [@OminousGMan](#):
>
> Is this the first time this has happened to you? If so when did it start?

Yes. As a result, I mentally attached the issue to the 0.39 story mode changes.

> [@OminousGMan](#):
>
> If this continues please let us know, hopefully this will resolve itself like most connection issues do.

I’ll run another character across the same section of story and see if that issue occurs again. It could very well have been tied to the AWS issues from earlier this month.
