https://community.appian.com/discussions/f/data/20066/query-achieved-detailsHi All, I have a requirement to query details once the process is achieved. I understand that, once data is archived, it moves to disk and using smart service we can un-archive data which appian will display in monitoring console. With help of reporten-USTelligent Community 12https://community.appian.com/thread/78447?ContentTypeID=1Sat, 12 Dec 2020 02:11:40 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:1d3d7a29-08ae-4d97-9276-a043c9752eecChristineLHutchison<p>A common design approach is to create DB tables to persist the data that you want to report on, especially if it is long term. So, if you want to report on process instance data, you can configure that process to put the data into a CDT that is is a DS and use write to datastore. Then, you will not need to introduce manual activities like unarchiving KDBs, etc.</p><div style="clear:both;"></div>https://community.appian.com/thread/78438?ContentTypeID=1Fri, 11 Dec 2020 14:46:16 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:ec0d8c6f-5226-4f8f-97cf-8d9bda397204Stewart Burchell<p>I would suggest you rethink the design. If you&#39;re wanting to query details about a process instance that has long been archived then perhaps you store the relevant details in a database table where you can access the data, and manage it (e.g. keep on disk for 3 years and then delete). But even that seems a long time to be keeping data for about a process instance. What sort of data are you talking about and why do you need to retrieve it after the process has completed? That is: what&#39;s the Use Case you have?</p><div style="clear:both;"></div>