--- title: "Process incidents with the after parameter" slug: "process-incidents-with-the-after-parameter" tags: ["Product Usage", "SaaS"] updated: 2026-09-01T09:28:14Z published: 2026-09-01T09:28:14Z canonical: "docs.trellix.com/process-incidents-with-the-after-parameter" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Process incidents with the after parameter The most reliable method to process incidents from the events API is to use a pagination cursor from the `after` parameter. This method ensures that incidents aren't skipped or duplicated due to the lack of time stamp precision. These are the general sequence of steps to follow when applying the `after` parameter: 1. Issue an initial request using the request parameters and `since` with a value set to a date in the last 60 minutes. 2. Retrieve the next page of incidents through the **Link** response header value within the `next` link relationship. 3. Issue the paginated request. 4. Pause and repeat step 2. > [!NOTE] > Note > > If there is no `next` link in the response header, you have received all incidents for the time period specified in the original request.