You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sources/platform/storage/usage.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -131,17 +131,22 @@ Go to the [API documentation](/api/v2#rate-limiting) for details and to learn wh
131
131
132
132
## Data retention
133
133
134
-
Apify securely stores your ten most recent runs indefinitely, ensuring your records are always accessible. Unnamed datasets and runs beyond the latest ten will be automatically deleted after 7 days unless otherwise specified. Named datasets are retained indefinitely.
134
+
On the free plan, Apify stores the ten most recent runs for a maximum of 4 months. On paid plans, the retention period of the plan applies. Unnamed storages and runs beyond the latest ten will be automatically deleted according to these retention periods. Named storages are retained indefinitely.
135
135
136
136
### Preserving your storages
137
137
138
-
To ensure indefinite retention of your storages, assign them a name. This can be done via Apify Console or through our API. First, you'll need your store's ID. You can find it in the details of the run that created it. In Apify Console, head over to your run's details and select the **Dataset**, **Key-value store**, or **Request queue** tab as appropriate. Check that store's details, and you will find its ID among them.
138
+
To ensure indefinite retention of selected storages, assign them a name. This can be done via Apify Console or through our API.
139
139
140
-

140
+
1. In [Apify Console](https://console.apify.com), head over to your run's details and select the **Dataset**, **Key-value store**, or **Request queue** tab as appropriate.
141
+
1. Check that store's details to find its ID:
141
142
142
-
Find and open your storage by clicking the ID, click on the **Actions** menu, choose **Rename**, and enter its new name in the field. Your storage will now be preserved indefinitely.
143
+

143
144
144
-
To name your storage via API, get its ID from the run that generated it using the [Get run](/api/v2/actor-run-get) endpoint. You can then give it a new name using the `Update \[storage\]` endpoint. For example, [Update dataset](/api/v2/dataset-put).
145
+
1. Click the ID to open the storage details.
146
+
1. Click on the **Actions** menu and choose **Rename**.
147
+
1. Enter a new name in the field. Your storage will now be preserved indefinitely.
148
+
149
+
To name your storage via API, get its ID from the run that generated it using the [Get run](/api/v2/actor-run-get) endpoint. You can then give it a new name using the `Update [storage]` endpoint. For example, [Update dataset](/api/v2/dataset-put).
145
150
146
151
Our SDKs and clients each have unique naming conventions for storages. For more information check out documentation:
0 commit comments