### Author:  [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [August 21, 2023, 11:10pm UTC](https://meta.discourse.org/t/weird-bug-with-discourse-assign/276109/2 "2023-08-21T23:10:35Z")
yea the console is showing errors here.
>
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 21, 2023, 11:38pm UTC](https://meta.discourse.org/t/weird-bug-with-discourse-assign/276109/3 "2023-08-21T23:38:11Z")
Its a small action with no action code!
You can fix this using the console, enter the container find the small actions on the topic, one of them is missing an action code.
We should probably add a sql validation to ensure this is impossible.
---
### Author:  [@hello-smile6](https://meta.discourse.org/u/hello-smile6)
#### Post date: [August 21, 2023, 11:39pm UTC](https://meta.discourse.org/t/weird-bug-with-discourse-assign/276109/4 "2023-08-21T23:39:04Z")
> [@sam](#):
>
> Its a small action with no action code!
I think those can be created using the API (we have a theme component that creates one), will we have to manually run some kind of database migration?
---
### Author:  [@hello-smile6](https://meta.discourse.org/u/hello-smile6)
#### Post date: [August 21, 2023, 11:42pm UTC](https://meta.discourse.org/t/weird-bug-with-discourse-assign/276109/5 "2023-08-21T23:42:04Z")
Here’s an example of another one created using our theme component:
[https://amcforum.wiki/t/is-this-what-it-looks-like/1846](https://amcforum.wiki/t/is-this-what-it-looks-like/1846)
---
### Author:  [@hello-smile6](https://meta.discourse.org/u/hello-smile6)
#### Post date: [August 21, 2023, 11:48pm UTC](https://meta.discourse.org/t/weird-bug-with-discourse-assign/276109/6 "2023-08-21T23:48:25Z")
> [@hello-smile6](#):
>
> we have a theme component that creates one
It seems like 25 different topics all have posts that are breaking discourse-assign, according to the results of this SQL query (using [data explorer](https://meta.discourse.org/t/32566?silent=true)):
```sql
SELECT id topic_id FROM topics topic WHERE topic.id IN (SELECT topic_id FROM posts WHERE post_type = 3 AND action_code IS NULL)
```
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 21, 2023, 11:48pm UTC](https://meta.discourse.org/t/weird-bug-with-discourse-assign/276109/7 "2023-08-21T23:48:39Z")
GPT bot to the rescue…
> [@On another topic](https://meta.discourse.org/t/276113/6):
>
> Thank you for the additional information. Given the code snippet from the `topic.rb` file, it’s clear that small actions are indeed created as a type of post with `post_type` set to `Post.types[:small_action]` and an `action_code` associated with it.
>
> If we want to find small actions with no `action_code`, we can adjust the query to look for posts where `post_type` is `3` (small action) and `action_code` is `nil`.
>
> Here are the revised steps:
>
> 1. **Enter the container** : You can enter the container by using the command `./launcher enter app` from the command line in your Discourse directory.
> 2. **Run `rails c`** : Once inside the container, you can start the Rails console by running the command `rails c`.
> 3. **Find the Topic** : To find the topic, you can use the `Topic.find_by(id: your_topic_id)` command. Replace `your_topic_id` with the ID of the topic you are looking for.
> 4. **Find the Small Action with no `action_code`** : Small actions are stored in the `posts` table with `post_type` set to `3` and `action_code` is `nil`. You can find the small action related to your topic with `sa = Post.where(topic_id: your_topic_id, post_type: 3, action_code: nil)`.
> 5. **Delete the Small Action** : Once you have the small action, you can delete it by running `sa.destroy_all`.
>
> Please make sure to replace `your_topic_id` with the actual ID of your topic. Also, be careful when deleting records, as it can’t be undone.
>
> Let me know if you have any questions or need further assistance!
---
### Author:  [@Firepup650](https://meta.discourse.org/u/Firepup650)
#### Post date: [August 22, 2023, 1:25am UTC](https://meta.discourse.org/t/weird-bug-with-discourse-assign/276109/8 "2023-08-22T01:25:34Z")
If that’s the check, why not just add `!!post.actionCode` to the if block?
---
### Author:  [@Firepup650](https://meta.discourse.org/u/Firepup650)
#### Post date: [September 12, 2023, 11:07am UTC](https://meta.discourse.org/t/weird-bug-with-discourse-assign/276109/9 "2023-09-12T11:07:36Z")
Finally got around to this, and PR’d a change:
[https://github.com/discourse/discourse-assign/pull/509](https://github.com/discourse/discourse-assign/pull/509)