MAX delay of events for system logs polling

Hi,

I’m working on an app that consumes a stream of events from the /api/v1/logs endpoint via polling requests. The app is designed to only process events that are no older than 24 hours, based on the published field in the response, which we treat as the event’s timestamp.

Recently, we noticed that some events fetched via polling from the oktapreview domain had a published timestamp older than 24 hours. Could this also happen in production (okta domain)? Or is that some outlier behavior that appeared on testing env only?

Is there any defined maximum delay between when an event is published (the published timestamp) and when it becomes available through the polling API? If so, is this documented anywhere?

Thanks!

Thank you for reaching out here on the Okta Developer Forum. We noticed that your question is more closely related to APIs and log events. To ensure you receive the most accurate and timely assistance, we recommend reposting your query on Okta’s Community at: Okta Help Center (Lightning)

Okta’s teams on the Community are better equipped to provide the comprehensive support and guidance you need as they have the specialized knowledge and expertise in APIs and log events.

We appreciate your understanding and are committed to ensuring you receive the best possible support. If you have any other questions or issues related to Okta’s developer tools and API’s, feel free to post them here, and we’ll be happy to assist!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.