# Inconsistent number of columns found

**URL:** <https://community.seqera.io/t/inconsistent-number-of-columns-found/1639>\
**Category:** Ask for help\
**Tags:** multiqc\
**Created:** [January 23, 2025, 1:41am UTC](https://community.seqera.io/t/inconsistent-number-of-columns-found/1639 "2025-01-23T01:41:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hanjiewu](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/hanjiewu/32/678_2.png) [@Hanjiewu](https://community.seqera.io/u/Hanjiewu)\
**Post date:** [January 23, 2025, 1:41am UTC](https://community.seqera.io/t/inconsistent-number-of-columns-found/1639/1 "2025-01-23T01:41:52Z")

</div>

I upgraded MultiQC to version 1.26 yesterday, but one of my custom reports was skipped, and the message displayed was: “Inconsistent number of columns found in amr\_combined.tsv” I’m not sure what went wrong with this particular table, as the other tables had no issues. The code (shown below) wasn’t changed and worked fine with version 1.24. I upgraded to version 1.27 today, but the problem persists.  
[amr\_combined.tsv](https://community.seqera.io/uploads/short-url/1n1jP42Yvn1nOV2bkwzPtyJ2Dqc.tsv) (2.1 MB)

```auto
 amr_results:
        parent_id: 'Other species'
        parent_name: "Other species grouped data"
        parent_description: "Other species grouped data contains MLST, AMR and VFDB sub-sections below it"
        id: 'amr_results'
        section_name: 'amr_results'
        description: "Antimicrobial resistance and Virulence factors prediction"
        plot_type: 'table'

```

---

<div class="post-metadata">

**Author:** ![vlad.savelyev](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/vlad.savelyev/32/576_2.png) [@vlad.savelyev](https://community.seqera.io/u/vlad.savelyev)\
**Post date:** [January 23, 2025, 1:50pm UTC](https://community.seqera.io/t/inconsistent-number-of-columns-found/1639/3 "2025-01-23T13:50:34Z")

</div>

Ah, managed to reproduce the issue! Sorry about it. MultiQC strips the trailing spaces, and in your table some rows have empty values in the last column, which leads to the inconsistent number of values after splitting the row.

Fixed this here: [Parsing custom content TSV: allow leading empty columns by vladsavelyev · Pull Request #3059 · MultiQC/MultiQC · GitHub](https://github.com/MultiQC/MultiQC/pull/3059)

---

<div class="post-metadata">

**Author:** ![Hanjiewu](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/hanjiewu/32/678_2.png) [@Hanjiewu](https://community.seqera.io/u/Hanjiewu)\
**Post date:** [January 24, 2025, 12:59am UTC](https://community.seqera.io/t/inconsistent-number-of-columns-found/1639/4 "2025-01-24T00:59:17Z")

</div>

Thank you for the quick fix. One more thing: what is the limitation on the number of samples allowed for an interactive table? Is there a way to bypass this mechanism?

 ![Screenshot 2025-01-24 at 8.50.05 AM](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/2X/f/fd814c0909fbb05c8dc7cd0eaa6608d06e01902b.png)

---

<div class="post-metadata">

**Author:** ![ewels](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/ewels/32/1_2.png) [@ewels](https://community.seqera.io/u/ewels)\
**Post date:** [January 28, 2025, 10:21am UTC](https://community.seqera.io/t/inconsistent-number-of-columns-found/1639/5 "2025-01-28T10:21:46Z")

</div>

Yes, using the config option `max_table_rows`. See the docs for more details:

> **[Configuration | Seqera Docs](https://docs.seqera.io/multiqc/getting_started/config#tables--violin-plots)**
>
> Settings to tweak how MultiQC works

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/system/32/2402_2.png) [@system](https://community.seqera.io/u/system)\
**Post date:** [February 4, 2025, 10:21am UTC](https://community.seqera.io/t/inconsistent-number-of-columns-found/1639/6 "2025-02-04T10:21:56Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.