# M+ not properly parsing

**URL:** <https://forums.combatlogforums.com/t/m-not-properly-parsing/12954>\
**Category:** General\
**Created:** [September 8, 2022, 11:17pm UTC](https://forums.combatlogforums.com/t/m-not-properly-parsing/12954 "2022-09-08T23:17:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kalanndok](https://avatars.discourse-cdn.com/v4/letter/k/ba8739/32.png) [@Kalanndok](https://forums.combatlogforums.com/u/Kalanndok)\
**Post date:** [September 8, 2022, 11:17pm UTC](https://forums.combatlogforums.com/t/m-not-properly-parsing/12954/1 "2022-09-08T23:17:34Z")

</div>

I just uploaded a log for an m+ run of mechagon-workshop.

The result unfortunately was this: [Warcraft Logs - Combat Analysis for Warcraft](https://www.warcraftlogs.com/reports/HWQAPhvLX8RY7Kjr)

It didn’t identify as a complete m+ run.  
I had that problem basicly with all m+ runs since September.

Is that a known issue or something that I need to fix clientside?

---

<div class="post-metadata">

**Author:** ![katskratches](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.combatlogforums.com/katskratches/32/1908_2.png) [@katskratches](https://forums.combatlogforums.com/u/katskratches)\
**Post date:** [September 11, 2022, 11:35pm UTC](https://forums.combatlogforums.com/t/m-not-properly-parsing/12954/2 "2022-09-11T23:35:07Z")

</div>

Do you log using an auto-logger? Many popular addons have settings that will turn on and off logging when entering or leaving combat. Try turning these settings off and manually logging a dungeon to see if it fixes your issue.
