# Delete row returning 502 bad getaway

**URL:** https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561
**Category:** Technical Help
**Tags:** event, delete
**Created:** [June 18, 2026, 12:44pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561 "2026-06-18T12:44:27Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![Lorenzo](https://community.baserow.io/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lorenzo](https://community.baserow.io/u/Lorenzo)
#### Post date: [June 18, 2026, 12:44pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/1 "2026-06-18T12:44:27Z")

</div>

### Are you using our SaaS platform ([Baserow.io](http://Baserow.io)) or self-hosting Baserow?

SaaS

### What are the exact steps to reproduce this issue?

I configured a delete as column of the grid and the event to me looks correct. what is wrong here?  
i can not understand it honestly. both claude opus 4.8 and kuma (gpt-4) are not helpful.  
the 502 error does not look to be my fault (?)

### Attach screenshots, videos, or logs that demonstrate the issue.

 ![Screenshot 2026-06-18 at 14.20.30.png](https://community.baserow.io/uploads/default/original/2X/d/db549640d20c5dae0f30d4436aa43bae211e859b.png) ![Screenshot 2026-06-18 at 14.20.07.png](https://community.baserow.io/uploads/default/original/2X/e/ee72f5e83de3d1d4f21eb503cc44aca5da652f49.png) ![Screenshot 2026-06-18 at 14.23.49.png](https://community.baserow.io/uploads/default/original/2X/9/9a85b74eacd952180d83a9e7cee179de8db778d3.png)

---

<div class="post-metadata">

### Author: ![picklepete](https://community.baserow.io/user_avatar/community.baserow.io/picklepete/32/5332_2.png) [@picklepete](https://community.baserow.io/u/picklepete)
#### Post date: [June 18, 2026, 12:45pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/2 "2026-06-18T12:45:41Z")

</div>

Hello @Lorenzo,

Please accept my apologies for the inconvenience, we are investigating this at the moment. I’ll report back here when it’s resolved.

Cheers,

Peter

---

<div class="post-metadata">

### Author: ![Lorenzo](https://community.baserow.io/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lorenzo](https://community.baserow.io/u/Lorenzo)
#### Post date: [June 18, 2026, 12:53pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/3 "2026-06-18T12:53:26Z")

</div>

i forgot to mention that the record is actually deleted despite the operation request returning 502. bc of the error the grid is not reloaded (f5 will ask for the login again). the only thing that works is changing page (or view as you call it here)

---

<div class="post-metadata">

### Author: ![khalil.io](https://community.baserow.io/user_avatar/community.baserow.io/khalil.io/32/4873_2.png) [@khalil.io](https://community.baserow.io/u/khalil.io)
#### Post date: [June 18, 2026, 9:23pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/4 "2026-06-18T21:23:18Z")

</div>

Hello @Lorenzo, I’ve had the same error: [Bug when deleting rows and updating rows with files](https://community.baserow.io/t/bug-when-deleting-rows-and-updating-rows-with-files/12557)

In my case, an error also appeared when updating rows that contain files.

Thanks, @picklepete, for the support!

---

<div class="post-metadata">

### Author: ![picklepete](https://community.baserow.io/user_avatar/community.baserow.io/picklepete/32/5332_2.png) [@picklepete](https://community.baserow.io/u/picklepete)
#### Post date: [June 19, 2026, 8:29am UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/5 "2026-06-19T08:29:25Z")

</div>

Good morning @Lorenzo and @khalil.io,

Some good news: I can confirm that the row deletion is a bug, but it’s isolated to just the application builder, it still works in automations. The action _does still delete the row_, but an error pop-up is shown, which is inaccurate.

The bad news: a fix today is unlikely, we will need to investigate this deeper early next week.

Please accept my apologies for the inconvenience, we’ll hopefully have it resolved very soon.

Cheers,

Peter

---

<div class="post-metadata">

### Author: ![Lorenzo](https://community.baserow.io/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lorenzo](https://community.baserow.io/u/Lorenzo)
#### Post date: [June 22, 2026, 3:04pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/6 "2026-06-22T15:04:55Z")

</div>

hey @picklepete how are the fixes going? have you (or Claude 😉) started the fixing session?  
can we still expect a fix early this week?

thanks!

---

<div class="post-metadata">

### Author: ![picklepete](https://community.baserow.io/user_avatar/community.baserow.io/picklepete/32/5332_2.png) [@picklepete](https://community.baserow.io/u/picklepete)
#### Post date: [June 22, 2026, 3:06pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/7 "2026-06-22T15:06:13Z")

</div>

Hi @Lorenzo,

It’s fixed and awaiting deployment, which should hopefully happen tomorrow. Thanks again for your patience, I hope it hasn’t caused too much inconvenience!

Cheers,

Peter

---

<div class="post-metadata">

### Author: ![Lorenzo](https://community.baserow.io/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lorenzo](https://community.baserow.io/u/Lorenzo)
#### Post date: [June 24, 2026, 8:49am UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/8 "2026-06-24T08:49:17Z")

</div>

I’m sorry to bother you @picklepete , i would like to know about the fix and if the publish of it could be causing:

 ![image](https://community.baserow.io/uploads/default/original/2X/3/3eae842dc67b6b3e1643d1649855f8b334a072b3.png)  
Thanks in advance,  
Lorenzo

---

<div class="post-metadata">

### Author: ![picklepete](https://community.baserow.io/user_avatar/community.baserow.io/picklepete/32/5332_2.png) [@picklepete](https://community.baserow.io/u/picklepete)
#### Post date: [June 24, 2026, 9:07am UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/9 "2026-06-24T09:07:51Z")

</div>

Hi @Lorenzo!

That’s a strange one! A fix for the delete row action was deployed yesterday.

Would you mind opening your developer tools console (e.g. in Chrome: `View` → `Developer` → `Developer Tools`) and screenshotting the request which failed? Like this:

 ![Screenshot 2026-06-24 at 10.06.37](https://community.baserow.io/uploads/default/original/2X/1/1adcdef2eea2f8433156d42e3da5ba3b34c1f1bf.png)

It’s possible that it’s unrelated to the delete row issue, but we’ll see!

Cheers,

Peter

---

<div class="post-metadata">

### Author: ![Lorenzo](https://community.baserow.io/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lorenzo](https://community.baserow.io/u/Lorenzo)
#### Post date: [June 24, 2026, 11:47am UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/10 "2026-06-24T11:47:33Z")

</div>

Totally right:

 ![image](https://community.baserow.io/uploads/default/original/2X/e/ed1eadf270613860c7e8f8557b1d1b86e2790099.png)  
these are all the network requests from the opening of the publish popup to the end of the publish. as you can see no errors here but in the console i have, per try, this error:

```bash
Uncaught (in promise) TypeError: this.$el.querySelector is not a function
    at Proxy.focusOnError (error.js:67:30)
    at Proxy.<anonymous> (error.js:57:33)

```

i hope this can help, might it be a case of: fixed a bug → created a bug? 😆

good luck on this!

---

<div class="post-metadata">

### Author: ![picklepete](https://community.baserow.io/user_avatar/community.baserow.io/picklepete/32/5332_2.png) [@picklepete](https://community.baserow.io/u/picklepete)
#### Post date: [June 24, 2026, 1:19pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/11 "2026-06-24T13:19:07Z")

</div>

Thanks @Lorenzo,

Judging by that screenshot, it looks like the publish (the `async` one, second from the top) was successful. Can you confirm by looking at the published application if it looks right?

If it has been published correctly, this is a frontend issue, unrelated to the delete-row issue, which we can also investigate.

Cheers,

Peter

---

<div class="post-metadata">

### Author: ![Lorenzo](https://community.baserow.io/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lorenzo](https://community.baserow.io/u/Lorenzo)
#### Post date: [June 24, 2026, 1:25pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/12 "2026-06-24T13:25:33Z")

</div>

sorry for not having mentioned it, but the deploy actually fails. the modifications applied to the project are not being reflected in the published version.

Cheers,  
Lorenzo

---

<div class="post-metadata">

### Author: ![picklepete](https://community.baserow.io/user_avatar/community.baserow.io/picklepete/32/5332_2.png) [@picklepete](https://community.baserow.io/u/picklepete)
#### Post date: [June 24, 2026, 1:27pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/13 "2026-06-24T13:27:57Z")

</div>

No problem at all! Would you mind publishing again with the Network tab open, and when you see the `async/` request, sending me a screenshot like this?

 ![image](https://community.baserow.io/uploads/default/original/2X/a/a5288b80b963b1942f1042f66b658f5934b9080b.png)

That `Response` tab should shed more light on what your issue is, unfortunately at the moment I don’t have many clues!

Cheers,

Peter

---

<div class="post-metadata">

### Author: ![Lorenzo](https://community.baserow.io/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lorenzo](https://community.baserow.io/u/Lorenzo)
#### Post date: [June 24, 2026, 1:30pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/14 "2026-06-24T13:30:21Z")

</div>

here it is:

 ![image](https://community.baserow.io/uploads/default/original/2X/5/5c133cea27bfebbf08e634899ffbe1018932fe54.png)

let me know if i can help in any other way

---

<div class="post-metadata">

### Author: ![picklepete](https://community.baserow.io/user_avatar/community.baserow.io/picklepete/32/5332_2.png) [@picklepete](https://community.baserow.io/u/picklepete)
#### Post date: [June 24, 2026, 1:32pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/15 "2026-06-24T13:32:17Z")

</div>

Grazie! And one more: if you open the `jobs/?job_ids=707363` (just before the last entry), what does that `Response` tab show?

Cheers,

Peter

---

<div class="post-metadata">

### Author: ![Lorenzo](https://community.baserow.io/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lorenzo](https://community.baserow.io/u/Lorenzo)
#### Post date: [June 24, 2026, 1:38pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/16 "2026-06-24T13:38:20Z")

</div>

I’m sorry, i had to redo the publish:

 ![image](https://community.baserow.io/uploads/default/original/2X/6/6914041bb91d8d1116bb008d0d03cb7ae6dc2bf4.png)  
this is the response of the last [https://api.baserow.io/api/jobs/?job\_ids=707371](https://api.baserow.io/api/jobs/?job_ids=707371)  
```json  
{  
“jobs”: [  
{  
“id”: 707371,  
“type”: “publish\_domain”,  
“progress\_percentage”: 100,  
“state”: “failed”,  
“human\_readable\_error”: “Something went wrong during the publish\_domain job execution.”,  
“created\_on”: “2026-06-24T13:33:50.346387Z”,  
“updated\_on”: “2026-06-24T13:34:02.337028Z”  
}  
]  
}  
```

all the other requests have the same data except for the “progress\_percentage” value that increases and the “human\_readable\_error” that is populated only in the last request.

---

<div class="post-metadata">

### Author: ![picklepete](https://community.baserow.io/user_avatar/community.baserow.io/picklepete/32/5332_2.png) [@picklepete](https://community.baserow.io/u/picklepete)
#### Post date: [June 24, 2026, 1:47pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/17 "2026-06-24T13:47:44Z")

</div>

Thank you @Lorenzo! I can see, using `707371`, that your issue is to do with a formula.

Have you recently editted formula where you’ve put a `$` symbol into it? If you could share where that is, and what element it’s used by, that’d be great!

Cheers,

Peter

---

<div class="post-metadata">

### Author: ![picklepete](https://community.baserow.io/user_avatar/community.baserow.io/picklepete/32/5332_2.png) [@picklepete](https://community.baserow.io/u/picklepete)
#### Post date: [June 24, 2026, 2:11pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/18 "2026-06-24T14:11:47Z")

</div>

Hey @Lorenzo, I can see the problem.

You have a formula somewhere that goes: `$formula: [form data]`. This is a bug introduced by Kuma when it assisted you at some point. If you manually remove the `$formula:` prefix, it’ll publish. We’ll work on addressing the Kuma part soon.

Cheers,

Peter

---

<div class="post-metadata">

### Author: ![Lorenzo](https://community.baserow.io/letter_avatar_proxy/v4/letter/l/4da419/32.png) [@Lorenzo](https://community.baserow.io/u/Lorenzo)
#### Post date: [June 24, 2026, 2:27pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/19 "2026-06-24T14:27:03Z")

</div>

ok, thanks, i will check and try to locate the formula. do not know at the moment where it could be located at.

you surely have to address kuma, it hallucinates a lot and 7/10 times does not answer and asks for a new session, cool idea in theory, unfortunate result.  
it would be really helpful if it worked better. Can i also suggest an MCP?  
ps: i know the main driver for gpt 4 models is cost, are you trying internally run AI?

have a wonderful day  
Lorenzo

EDIT:  
I can not find where the modification was made: kuma touched only 1 page and only 1 input in it. i verified it and it looks good to me, i tried also to reassign the value to the field. no success.

EDIT 2:  
would you be open for a google meet call to try resolving this issue? if not it’s fine and thanks for all the work you’re doing for me 😃

---

<div class="post-metadata">

### Author: ![picklepete](https://community.baserow.io/user_avatar/community.baserow.io/picklepete/32/5332_2.png) [@picklepete](https://community.baserow.io/u/picklepete)
#### Post date: [June 24, 2026, 2:44pm UTC](https://community.baserow.io/t/delete-row-returning-502-bad-getaway/12561/20 "2026-06-24T14:44:25Z")

</div>

> [@Lorenzo](#):
>
> you surely have to address kuma, it hallucinates a lot and 7/10 times does not answer and asks for a new session, cool idea in theory, unfortunate result.  
> it would be really helpful if it worked better.

I totally agree, my apologies for any inconvenience! We definitely want to iterate on Kuma’s abilities, every few releases it gets new superpowers 😬

> [@Lorenzo](#):
>
> Can i also suggest an MCP?

We [already support an MCP server](https://baserow.io/user-docs/mcp-server) 🚀

> [@Lorenzo](#):
>
> ps: i know the main driver for gpt 4 models is cost, are you trying internally run AI?

The model selection for Kuma has to juggle a few criteria, and cost / performance are careful things to dial in.

> [@Lorenzo](#):
>
> EDIT:  
> I can not find where the modification was made: kuma touched only 1 page and only 1 input in it. i verified it and it looks good to me, i tried also to reassign the value to the field. no success.
> 
> EDIT 2:  
> would you be open for a google meet call to try resolving this issue? if not it’s fine and thanks for all the work you’re doing for me 😃

I’m very sorry, but not at the moment! If you click around data sources / elements / workflow actions, one of them will have a `$formula` prefix to it.

Cheers,

Peter
