# Topicslug with numbers gets translated into topic id?

**URL:** <https://meta.discourse.org/t/topicslug-with-numbers-gets-translated-into-topic-id/112491>\
**Category:** Product Support\
**Created:** [March 25, 2019, 9:51am UTC](https://meta.discourse.org/t/topicslug-with-numbers-gets-translated-into-topic-id/112491 "2019-03-25T09:51:43Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![pontus.dualdecade](https://avatars.discourse-cdn.com/v4/letter/p/f6c823/32.png) [@pontus.dualdecade](https://meta.discourse.org/u/pontus.dualdecade)\
**Post date:** [March 25, 2019, 9:51am UTC](https://meta.discourse.org/t/topicslug-with-numbers-gets-translated-into-topic-id/112491/1 "2019-03-25T09:51:43Z")

</div>

So, on our discourse server we use topic slugs like `123-region-2` this has been no issue until recently. Now it seems thats the discourse server, if it gets a request for example `5454-region-3` and that topic slug does not exist. It gets the topic with topic id `5454` and this creates a lot of problems.

Was there an update to this behaviour recently? We usually run `launcher rebuild` close to once a week so we have 2.3.0.beta5 right now.

Another theory might be that our 123 part in `123-region-2` is always higher than topic ids and they both have just been increasing causing no “collisions” but now that we added another region which starts of from 0 again we almost exclusively get collisions with existing topics.

Is there a way to make sure if we get `http://discourse.server.com/t/123-mytopicslug-2.json` and that topic does not exist we get a 404?

---

_[View the full topic](https://meta.discourse.org/t/topicslug-with-numbers-gets-translated-into-topic-id/112491)._