# Likely a bug: invalid input syntax for type uuid: ""

**URL:** <https://community.weweb.io/t/likely-a-bug-invalid-input-syntax-for-type-uuid/3453>\
**Category:** Ask us anything\
**Tags:** supabase\
**Created:** [July 10, 2023, 10:37am UTC](https://community.weweb.io/t/likely-a-bug-invalid-input-syntax-for-type-uuid/3453 "2023-07-10T10:37:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![michaeln](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/michaeln/32/8078_2.png) [@michaeln](https://community.weweb.io/u/michaeln)\
**Post date:** [July 10, 2023, 10:37am UTC](https://community.weweb.io/t/likely-a-bug-invalid-input-syntax-for-type-uuid/3453/1 "2023-07-10T10:37:51Z")

</div>

**Context**  
My app uses OpenAI to generate responses using an input the user fills out on the front-end of the app. The workflow looks something like this:

1. OpenAI chat completion (with inputs from user)
2. Iterator (for loop)
3. Supabase: Insert (within the iterator)  
3.a. For each response from OpenAI (can generate multiple responses at once), create a new table record

This has been working fine until late last week (I think up until the most recent WeWeb UI update? The update that made the editor panel on the right a more uniform charcoal grey).

**Issue**  
While going through the workflow, everything is fine until I get to the Supabase: Insert workflow action. The preceding chat completion and iterator actions do what they are supposed to. I’ve been receiving this error message

> invalid input syntax for type uuid: “”

I interpret this to mean that the data being fed to Supabase from WeWeb for the primary key field (‘id’) is a text value instead of whatever supabase uses for uuid fields. However, in the Insert workflow action in WeWeb, the ‘id’ field is left blank, with the placeholder text ‘gen\_random\_uuid()’.

Has anyone else experienced this issue recently?

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [July 10, 2023, 11:26am UTC](https://community.weweb.io/t/likely-a-bug-invalid-input-syntax-for-type-uuid/3453/2 "2023-07-10T11:26:30Z")

</div>

> [@michaeln](#):
>
> This has been working fine until late last week

Hi @michaeln 👋

If nothing changed on your side and it was working before, it’s probably a bug. Don’t hesitate to [report it here](https://support.weweb.io/) so the tech team can take a look.

---

<div class="post-metadata">

**Author:** ![justifi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/justifi/32/2846_2.png) [@justifi](https://community.weweb.io/u/justifi)\
**Post date:** [July 11, 2023, 4:36pm UTC](https://community.weweb.io/t/likely-a-bug-invalid-input-syntax-for-type-uuid/3453/3 "2023-07-11T16:36:35Z")

</div>

I have run into the same issue. Only select those fields for which you need to enter a value - anything with a `default` value in the database can be omitted.

In your case, ‘uncheck’ your `id` field under the `Fields` dropdown.

Initially `All Fields` are visible.

 ![supamkt WeWeb 2023-07-11 at 12.32.47 PM](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/b/b765a24c6b396f789664a1d81ef8418b753a6819.png)

instead —\>

 ![supamkt WeWeb 2023-07-11 at 12.33.10 PM](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/8/8f0422dd763690c424daa0148068b3767126b98d.png)

---

<div class="post-metadata">

**Author:** ![michaeln](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/michaeln/32/8078_2.png) [@michaeln](https://community.weweb.io/u/michaeln)\
**Post date:** [July 11, 2023, 9:45pm UTC](https://community.weweb.io/t/likely-a-bug-invalid-input-syntax-for-type-uuid/3453/4 "2023-07-11T21:45:58Z")

</div>

This worked! Thanks for the recommendation - didn’t even dawn on me.