# Adding new taxa to tree requires isHybrid checked; Sp7

**URL:** <https://speciforum.org/t/adding-new-taxa-to-tree-requires-ishybrid-checked-sp7/1022>\
**Category:** Get Help\
**Created:** [January 31, 2023, 6:26pm UTC](https://speciforum.org/t/adding-new-taxa-to-tree-requires-ishybrid-checked-sp7/1022 "2023-01-31T18:26:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cefuchs](https://avatars.discourse-cdn.com/v4/letter/c/a87d85/32.png) [@cefuchs](https://speciforum.org/u/cefuchs)\
**Post date:** [January 31, 2023, 6:26pm UTC](https://speciforum.org/t/adding-new-taxa-to-tree-requires-ishybrid-checked-sp7/1022/1 "2023-01-31T18:26:18Z")

</div>

Hi all! First post in the forums, so please let me know if I’m in the wrong place. Get help sounded about right, but this might also be more of a bug report…

I had to add to new taxa to our Taxon tree in Sp7 today and was unable to do so on both my work laptop (chrome) and mobile phone (over data, Firefox). Did not function via “Add Child” from the tree itself, while clicked on parent, or from the Determinations taxon field’s “+New” in its dropdown in the catalog object page.

Upon seeing the summary complaining about the “isHybrid” field being… unhappy (can’t recall the specific terminology), I tried saving the new taxon with isHybrid checked (although the species was not a hybrid).

with isHybrid checked, I was able to add each taxa. Then went back in to edit the taxa removing the TRUE check for isHybrid. My curator/Sp7 head has confirmed that “isHybrid is NOT marked as a required field in the schema config.”

I’ve downloaded the full error report, but the main issue seems to be this at the top:

```auto
{"message":["Error occurred fetching from https://fwri.specifycloud.org/api/specify/taxon/",{"type":"invalidResponseCode","statusText":["Invalid response code 500. Expected one of 200, 201, and 409.","\n This error may indicate a misconfiguration or a bug in Specify. Please\n double check your configuration and report this issue.\n ","Response:"]

```

Thanks all!

---

<div class="post-metadata">

**Author:** ![Grant](https://yyz1.discourse-cdn.com/flex029/user_avatar/speciforum.org/grant/32/4255_2.png) [@Grant](https://speciforum.org/u/Grant)\
**Post date:** [January 31, 2023, 7:27pm UTC](https://speciforum.org/t/adding-new-taxa-to-tree-requires-ishybrid-checked-sp7/1022/2 "2023-01-31T19:27:11Z")

</div>

Hi @cefuchs,

This is exactly the right spot for questions like this one!

This is a bug that was reported last week and is now resolved:

> <https://github.com/specify/specify7/issues/2868>
>
> \<img width="860" alt="image" src="https://user-images.githubusercontent.com/3725…6050/213967357-159fe921-37e7-49b3-b439-f28f731dc581.png"\>
> 
> To recreate, fill the form out as follows:
> 
> \<img width="896" alt="image" src="https://user-images.githubusercontent.com/37256050/213967406-86c0ea82-ad05-45f2-90e0-d2e531c6d955.png"\>
> 
> \[Specify 7 Crash Report - 2023-01-23T04 44 43.025Z.txt\](https://github.com/specify/specify7/files/10476828/Specify.7.Crash.Report.-.2023-01-23T04.44.43.025Z.txt)
> 
> \`\`\`
> IntegrityError at /api/specify/taxon/
> (1048, "Column 'IsHybrid' cannot be null")
> \`\`\`
> 
> This was introduced in \`v7.8.4\` as I can not recreate in 7.8.3.
> 
> @melton-jason

This error will no longer occur once your Specify 7 instance has been updated to `v7.8.5` (which is out now)!

If you are looking for a workaround until the update takes place, you can check and uncheck the Hybrid checkbox before saving a new record.

All Specify Cloud instances (including `fwri`) will be updated in the next 24-48 hours! Let me know if you would like me to push the update sooner!

Thank you for reaching out!

---

<div class="post-metadata">

**Author:** ![Grant](https://yyz1.discourse-cdn.com/flex029/user_avatar/speciforum.org/grant/32/4255_2.png) [@Grant](https://speciforum.org/u/Grant)\
**Post date:** [January 31, 2023, 8:17pm UTC](https://speciforum.org/t/adding-new-taxa-to-tree-requires-ishybrid-checked-sp7/1022/3 "2023-01-31T20:17:48Z")

</div>

Hi @cefuchs,

The instance is now updated! Let me know if you encounter this issue again!