We are currently using Genesys GDPR and Privacy APIs to manage user data, specifically for deletion and export operations. Our API workflow is structured as follows:
We initiate a new deletion request by making a POST request to the route "/api/v2/gdpr/requests." We specify the requestType as "GDPR_DELETE," and in return, we receive a unique requestId.
Deletion requests may take up to 30 days to complete. Therefore, we continually poll the system by using the GET request to check the status of the request. The endpoint for this is "/api/v2/gdpr/request/{requestId}."
While step 1 is functioning correctly, we are encountering an issue during the polling process. The error message we receive is as follows:
We kindly request your guidance and assistance in understanding and resolving this matter. Your expertise will be invaluable in overcoming this challenge and ensuring the smooth functioning of our processes.
A 404 indicates a problem with the client's request, specifically that the requested resource was not found. In your specific case, this would indicate that the request ID you're using in the path isn't valid. Check your application for errors that could be malforming your request path and ensure that the request you're making is exactly what you intend.
If you have verified that your application is bug-free and the ID that's being used is expected to be valid, please open a case with Genesys Cloud Care to investigate further. We do not have access to your org's data via the forum to be able to determine any cause for this issue; all we can do here is take the 404 at face value and assume it's a legitimate client error.
FWIW I tried to look up the context ID provided in your post, but it doesn't appear to exist in the US East environment (per your forum user profile) in the last 7 days. If you can update your profile for the correct region your org is in, that will help us be able to look up correlation IDs for you in the future.
The contextID in question pertains to "US West." I don't consider this to be an issue specific to our application, as nearly 5000 delete requests have been successful in the past. However, I did observe an intriguing pattern: all request IDs older than 30 days seem to fail with the same "Not found" error. Is there a specific timeframe beyond which request IDs cannot be queried?
I don't believe this is specifically documented for the API endpoint directly, but the dev team has confirmed that GDPR requests are expected to be cleaned up after 14 days. So getting a 404 for the request ID any time after 14 days is normal behavior. For exports, the export file is valid for 30 days but you have to have the link.
As stated previously, we do not have access to your org's data via the forum. You must open a case with Care to investigate issues with your GDPR requests.
Thanks, I will keep it in my mind. If I still can't resolve it, I will start the new thread and will explain my problem in brief.
Thanks, I will keep it in my mind. If I still can't resolve it, I will start the new thread and will explain my problem in brief. To teammates and professionals in need of coursework aid, I strongly recommend the coursework writing service available at the provided URL Coursework Writing Service Help From Experts. I've had a fantastic experience utilising their service, and I couldn't be happier with the job quality, speed, and professionalism of the authors. They go above and beyond to guarantee that your homework not only satisfies your standards, but also stands out in terms of research, depth, and originality.