404 when fetching status of bulk profile import job

Question

Hello,We have a process which posts bulk profile updates to customer Klaviyo instances daily.  This generally works as it should, but recently one customer’s jobs have started returning 404 status immediately after being submitted.  The bulk job submission returns a 200 response with a job id, but when using that job id to check the job’s status, the request returns 404, indicating that the job was never actually submitted.  I can’t get any information on the job or why it has failed to submit.  All other customers’ jobs run with no issue, and this customer’s jobs have run successfully in the past.  Is there anything I can do to troubleshoot this?Thanks!

NOAH MERCY · Accepted Answer

Hi ​@harrisontyb,Thanks for sharing the details! The 404 error for the bulk profile update jobs could indicate an issue specific to the customer's Klaviyo instance. Here’s how you can troubleshoot:Validate Job ID Immediately: After receiving the job ID in the 200 response, immediately check its status to confirm it’s being created successfully. This can help isolate where the issue occurs.Check API Rate Limits: If the customer’s account is submitting a large number of jobs, it’s possible they’ve hit an API rate limit. Confirm if their account exceeds limits and adjust the job submission frequency if necessary.Verify Data Payload: Ensure the data payload for the customer’s jobs is formatted correctly and adheres to Klaviyo’s API requirements. Invalid data could cause the job to fail silently.Account Configuration: Confirm that the customer’s Klaviyo instance hasn’t undergone changes, such as deactivating API credentials, modifying permissions, or adjusting settings.Contact Klaviyo Support: If the issue persists, provide Klaviyo Support with the affected job IDs, timestamps, and request/response logs. This will help them investigate further.Let me know if you’d like additional assistance!Best,NOAH

harrisontyb · Answer

Thanks for the response, ​@NOAH MERCY. It does seem that it was due to changes in the customer’s account, so no further investigation needed.

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials

Scanning file for viruses.

This file cannot be downloaded