Manage 429 Errors
If you receive a 429 error, it indicates that you have exceeded the allowed number of requests within a given time period. Follow these best practices to manage 429 errors effectively:
- Read the ‘Retry-After’ header: When a 429 error is returned, check the ‘Retry-After’ response header. This header specifies the time to wait before retrying the request.
- Implement retry logic: Use the ‘Retry-After’ value to implement retry logic in your application, ensuring that retries are attempted after the specified time to avoid subsequent 429 errors.
- Batch your requests: Avoid submitting numerous small requests in quick succession. Instead, batch multiple identities into a single request to reduce the frequency of calls and minimize the risk of hitting rate limits.
Dataset expiration
Set up automatic dataset cleanup for short-lived data. Use the /ttl
endpoint on the Data Hygiene API to schedule expiration dates for datasets for cleanup based on a specified time or date. See the Dataset expiration endpoint guide to learn how to create a dataset expiration and the accepted query parameters.
Monitor work order and dataset expiration status
You can efficiently monitor the progress of your data lifecycle management through the use of I/O Events. An I/O Event is a mechanism for receiving real-time notifications about changes or updates in various services within Experience Platform.
I/O Event alerts can be sent to a configured webhook to enable the automation of activity monitoring. To receive alerts via webhook, you must register your webhook for Experience Platform alerts in the Adobe Developer Console. See the guide on subscribing to Adobe I/O Event notifications for the detailed instructions.
Use the following data lifecycle methods and guidelines to effectively retrieve and monitor job statuses: