This "phenomenon" usually occurs when the train is not recognized internally as a passenger train. The default setting, whether a train is a travel or freight train, is based on the train type. If you have given the train an undefined genre (for example, the abbreviation of your company without defining it in the generic list), then the train will be interpreted as a freight train on the safe side. However, freight trains can not have any stops on demand.

You've got the following possibilities:

a. Define the desired genus in the FBS genre and train number directory as a travel train.

b. You can override the default setting for the train type by going to the register page Other in the train data window. There is the option field "Calculate train drag for ...travel train / freight train". After you change the train type, reassign the halt list and route so that the change takes effect for the holding type.

c. Especially for trains on the infrastructure of DB Netz, it is possible to distinguish conceptually between genre and product: genre is the "internal business" for the railway operators (in particular for the dispatcher), product is the traffic for the travelers. Give your train, e.g. the genus DPE and as a product your company abbreviation. DB Netz "sees" only the genre, the traveler "sees" only the product. In this way, a train can also be entered with traction parts of different TOCs, for example, the trains between Erfurt and Plaue (Thuringia), which consist of EB and STB.

Furthermore, it should be noted that only stops with a duration of stay < 1 min can be automatically marked as demand halts and these halts must not simultaneously be operating stops.