Hello Genesys Team,
We're currently using the Genesys Cloud Python SDK to retrieve historical adherence data using the following endpoints:
POST /api/v2/workforcemanagement/adherence/historical/bulk
GET /api/v2/workforcemanagement/adherence/historical/bulk/jobs/{jobId}
According to the official documentation, the maximum supported time range for this request is 31 days. However, we've encountered an issue where some adherence data is missing when using the full 31-day interval, even though the job status returned is "Complete" and the download URLs are provided.
What We Observed:
When submitting a request with a 31-day interval (e.g., Dec 1 to Dec 31), certain user adherence data for specific days (e.g., Dec 19) is completely absent in the result.
When splitting the same query into two 15- or 16-day intervals, the missing data appears correctly in the partial results.
We found other developers in the community reporting similar experiences, suggesting this might be a known issue under certain load conditions.
Similar Issue
Questions:
1. Is this a known limitation or bug related to large volume adherence jobs over the full 31-day range?
2. Are there any internal buffer or processing constraints that might explain the loss of adherence data beyond a certain time span or data volume?
3. Are there official recommendations or best practices for querying adherence data in high-volume scenarios (e.g., limit to 15-day chunks)?
4. Is the product team actively working on improving this behavior or documenting a recommended maximum range for reliability?
We're currently considering adjusting our system to automatically chunk these requests into smaller periods, but would prefer guidance from Genesys to ensure we're aligning with platform expectations and roadmaps.
Thanks in advance for your feedback.
#PlatformSDK------------------------------
Ing. Edwin Moreno Ramos
------------------------------