The Job/Queue status does not update/refresh automatically in Orchestrator. The user need to manually refresh it to get the correct status. In such situation we ask users to update value of maxQueryString and maxAllowedContentLength settings in request filtering. What is the significance & use of maxQueryString and maxAllowedContentLength settings in request filtering?
The "maxQueryString" and "maxAllowedContentLength" settings are related to configuring the maximum size of data that can be sent to the server via HTTP requests.
- maxQueryString:
- Significance: The "maxQueryString" setting defines the maximum length (in bytes) of the query string portion of a URL that the server will accept in an HTTP request. The query string is the part of a URL that follows the "?" character and includes key-value pairs used to pass data to the server.
- Relation to Job/Queue Auto Refresh: this setting may affect the job/queue auto-refresh functionality if the query string used for auto-refreshing jobs or queues becomes too large. If the query string exceeds the "maxQueryString" limit, it can lead to issues, such as incomplete or failed auto-refresh requests.
- maxAllowedContentLength:
- Significance: The "maxAllowedContentLength" setting defines the maximum size (in bytes) of the content that can be uploaded to the server in an HTTP request. It applies to file uploads and other content sent in the request body.
- Relation to Job/Queue Auto Refresh: While "maxAllowedContentLength" primarily affects file uploads and POST requests with large payloads, it may not have a direct impact on job/queue auto-refresh, which typically uses query parameters rather than request bodies.
Take the proper back up of web.config file then perform the changes as suggested. maxAllowedContentLength should already be there in file, so add the maxQueryString='2147483647'.