50 concurrent users is close to the top end of the performance profile for a single authoring instance. Which version of the software are you on? What sort of hardware are you running on - what number of CPUs and how much memory? How is your storage connected - do you have a fully optimized IO solut...

Have you looked not just at the bundles but also the services? Check the following:Is bundle A activeGo to services console - check to see if Service A is active and runningGo to the services console - check to see if Service B is active? If it isn't why - are there unfilled dependencies? Try to act...

I am not sure I fully understand you use case, but it sounds to my like what you are describing is something that falls under the Multi-Site Manager functionality. In you use case you have the same page in two locations, and one is the master and the other is a copy of the master and  you want to be...

As another user pointed out using the query string means you won't caching the results in dispatcher. Can you cache the results in your other layer? Or will the result of /shop/categoryA be cached in a CDN for example? You will want to think through the performance impact of this model and be sure y...

The short answer to you question is that I believe language copy actually kills the live copy relationship so no roll outs will impact the copy. In general language copy is intended to be used to create language copies when you want to do something like manual translation and you simply creating the...

Your first constraint shouldn't impact the proposed concept. A replication event listener can listen for either sent or receive events. So the replication event listener would sit on the publish servers and listen for replication received events - which are happening in your design. A replication ev...

There are probably a bunch of ways to handle it. The simplest way - assuming you have store all the information that is needed by Relay in the content you could write a replication event listener that runs on the publish instances and whenever it receives something it sends the response to Relay. Th...

The stale status is indicative of an error state. Essentially it means that the workflow instance is not going to be able to continue to run. One common reason for the stale state is that the payload of the workflow has been deleted or moved. Depending on the version you are running it may also indi...

My guess is that's probably the expected behavior. I don't know this for sure but my guess is that there is Modification Event Listener that listens for changes to the vanity URL property and updates the resource resolver configuration whenever changes are made to the content. Generally these kinds ...

You should always be configuring dispatcher at the publisher level - dispatcher in front of publisher instances is the standard approach - almost all the dispatcher documentation is geared towards how to configure dispatcher for a publisher instance. In addition to configuring dispatcher in front of...