/api/v2/workforcemanagement/businessunits/{businessUnitId}/weeks/{weekId}/schedules/{scheduleId}/agentschedules/query Output

Hello All,
When we developed a few months ago, calls to /api/v2/workforcemanagement/businessunits/{businessUnitId}/weeks/{weekId}/schedules/{scheduleId}/agentschedules/query were returning the full JSON response with shifts, etc. Now, it always writes the results to an AWS object with download redirect. Even with forceAsync=false&forceDownloadService=false. Why did this behavior change over time? Why can't this be overridden ?

TIA !

Those flags are for testing purposes only. There has been no related change. What you are likely hitting is that the result is too large to return 'inline'. As to why a previous query returned directly, it is because it had a smaller result.

From above the API Response section for this endpoint states:
downloadUrl (string) The URL from which to download the result if it is too large to pass directly.

Also, those two flags can be set to true when you want to force asynchronous and download service for cases where you are developing/testing with results that are small enough to be returned directly (because you want to test the async/download scenario). It does not make sense to set them to false in any circumstances - it will be ignored. I.e., forceAsync=false does not equate to force synchronous.

1 Like

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