# Bug found in delete button behaviour

**URL:** <https://forum.alumio.com/t/bug-found-in-delete-button-behaviour/3587>\
**Category:** Alumio Feedback\
**Tags:** bugs\
**Created:** [September 24, 2026, 8:38am UTC](https://forum.alumio.com/t/bug-found-in-delete-button-behaviour/3587 "2026-09-24T08:38:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jesse.wever](https://forum.alumio.com/user_avatar/forum.alumio.com/jesse.wever/32/296_2.png) [@jesse.wever](https://forum.alumio.com/u/jesse.wever)\
**Post date:** [September 24, 2026, 8:38am UTC](https://forum.alumio.com/t/bug-found-in-delete-button-behaviour/3587/1 "2026-09-24T08:38:51Z")

</div>

Hello,  
I think i have found a bug, when deleting routes from the routes overview using the delete button on the top right (next to the export button) it errors and doesn’t delete the routes. the error given is:

`An exception occurred while executing 'DELETE FROM di_object WHERE (((name LIKE ? AND disabled IN (?)) AND type = ?) AND identifier IN (?)) AND type = ? LIMIT 10000' with params ["%ep%", [true], "route-configuration", "NameOfRouteBeingDeletedWithEP", "route-configuration"]: SQLSTATE[22007]: Invalid datetime format: 1292 Truncated incorrect DOUBLE value: 'Array'`

it seems that the error only popups when filters have been applied to the overview, in this case name contains “EP” and disabled is true. when removing all filters delete button works again.

Our environment is on lts version 3.111.4 so the behaviour might already be patched in newer versions  
Greetings,  
Jesse

---

<div class="post-metadata">

**Author:** ![r.candrian](https://forum.alumio.com/user_avatar/forum.alumio.com/r.candrian/32/235_2.png) [@r.candrian](https://forum.alumio.com/u/r.candrian)\
**Post date:** [September 28, 2026, 7:43am UTC](https://forum.alumio.com/t/bug-found-in-delete-button-behaviour/3587/2 "2026-09-28T07:43:56Z")

</div>

Hi @jesse.wever,

Thank you for reporting this issue.

We tried to reproduce the issue in the latest version of Alumio, and we didn’t get the same issue. It might be because the issue has been fixed. The new LTS will be released next week; since it’s not blocking, we recommend waiting until your environment is updated.