Historics in queued status


i’ve created an historic using the api and i’ve created the subscription (s3 endpoint) too, now i have the playback historic id and the subscription id.
I’ve started the historic using the start() method and now i can see the historic in “queued” status.
I’ve started it at 11:10 in the morning and after 4 hours the historic is still in queued status, is it normal?

Many tnx



The Historics cluster is currently much busier than usual, with some jobs taking 24hrs or more before they begin being processed. We are making a number of improvements to the Historics service, including some massive performance enhancements, which we hope to be able to release within the coming months.