OpenShift idling, rationale - just a service differentiation? -

have found several q&a's related openshift's concept of application idling when there no inbound traffic 24 hours. apart fact there hacks work around it, wondering, effect since openshift claims application brought full live state when incoming request encountered. in case, apart fact http request causes application go idle state live/running state run trifle slower, there other inconvenience missing here ?

in experience, first call after idling consistently fails. subsequent calls work then. due timeout, since takes while spin gears. may depend on time application takes activate, meaning specific kind of application.

however switched free plan bronze while ago , did not experience problems since then.