# My Questdb table is suspended and I cannot resume it, how can I reset the errors?

**URL:** <https://community.questdb.com/t/my-questdb-table-is-suspended-and-i-cannot-resume-it-how-can-i-reset-the-errors/30>\
**Category:** Community\
**Tags:** storage, question\
**Created:** [June 26, 2024, 5:59pm UTC](https://community.questdb.com/t/my-questdb-table-is-suspended-and-i-cannot-resume-it-how-can-i-reset-the-errors/30 "2024-06-26T17:59:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex004/uploads/questdb/original/1X/b6b1b349e598d0550947e63d7923a9d7df0279eb.png) [@system](https://community.questdb.com/u/system)\
**Post date:** [June 26, 2024, 5:59pm UTC](https://community.questdb.com/t/my-questdb-table-is-suspended-and-i-cannot-resume-it-how-can-i-reset-the-errors/30/1 "2024-06-26T17:59:50Z")

</div>

I have a table in questdb and it is shown as a suspended table when I query

```auto
SELECT * from wal_tables()

```

I tried to resume with

```auto
ALTER TABLE trades RESUME WAL

```

but in a moment it changes the state back to suspended.

I think it started to happen after I ran an update statement and I now see some IdexOutOfBoundException exceptions in the server.log processing my update.

How can I ignore the offensive UPDATE and make the table accept the data again?

---

<div class="post-metadata">

**Author:** ![nwoolmer](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.questdb.com/nwoolmer/32/24_2.png) [@nwoolmer](https://community.questdb.com/u/nwoolmer)\
**Post date:** [June 26, 2024, 6:00pm UTC](https://community.questdb.com/t/my-questdb-table-is-suspended-and-i-cannot-resume-it-how-can-i-reset-the-errors/30/2 "2024-06-26T18:00:02Z")

</div>

If a WAL table stuck on one of the transactions there is a way to clear all the pending transactions by converting it to Non-WAL and back. It needs restarts though. Try this:

```auto
ALTER TABLE trades SET TYPE BYPASS WAL

```

Then restart QuestDB server. This will convert table to a non-WAL type and clears all the transactions kept in WAL files. Then you can convert it back

```auto
ALTER TABLE trades SET TYPE WAL

```

And then restart again. At this point your table is back to normal, you can insert data into it.

These `SET TYPE` alters don’t have any effect until restart, the conversions happen at the server startup.