Something we're noticing from the SA team when we work in our demos. I'm going to start with the steps to reproduce this bug

1.- Install experience and say you are working in your 'http://work.domain'

2.- After enabling properly the SiteFactory SiteAccess Matcher (https://github.com/ibexa/recipes/blob/master/ibexa/experience/3.3.16/config/packages/ezplatform.yaml#L68), go to the Site Factory list screen

3.- Create some content for your site skeleton if needed

4.- Add a new site, using that skeleton,  entering work.domain as the domain and the path you want to work with, let's say "test".

5.- Try to visit http://work.domain/test and you'll receive a 404

That's the bug. If you edit the site later and just save it, then going to http://work.domain/test will return a 200 as status code, as expected. This is why I think there's something related to caching when we create sites in this case of situation.