As services templates like services and elements live on specific DMAs, will it be definable in the swarming API that they can move like elements?
With most of our service templates we change inputs etc via automation scripts, so re-apply the service template to update the filtering of tables from the attached elements, reducing the subscriptions and alarm information that propagates through to the service, which is currently a single point of failure in this process if the hosting DMA for the template is offline.
In the future, swarming will indeed also be possible for services (including service templates).
Service templates are not technically hosted anywhere (any agent can apply them), but the template definition is linked to a single agent which indeed might make it unavailable while that remote agent is down (if the agents didn't have contact before).
Since you're running service templates from automation scripts, it might be a good idea to check whether the TryCreateService message being used has a HostingAgentID / DataMinerID filled out. If it has, my recommendation would be to remove these, as having these will force the request to go towards that specific agent. If that agent is down, it will not be able to execute the request. If the fields are not filled out, the agent running the automation script will apply the service template instead. If that agent still has the service template definition in memory, that would be one less point of failure.