Adjusting Default HTTP Timeouts

It may become necessary to change the default HTTP Timeouts used by Vera when receiving and sending HTTP messages to other systems. This can be useful when troubleshooting communication errors seen when routing large records from qTest or Jira.

To change the HTTP Timeouts, use the following Environment Variables in your docker-compose.yml file under the Vera Server configuration settings (or specific modules used for Jira or qTest). The value is in seconds and should only contains whole numbers.

Environment Variable	Description	Default Value (seconds)

Environment Variable	Description	Default Value (seconds)
`DEFAULT_HTTP_TIMEOUT`	The overall default timeout. This will affect all HTTP communications from Vera unless specifically overridden by the variables below.	100
`QTEST_CLIENT_HTTP_TIMEOUT`	HTTP timeout for communications to qTest servers only.	`DEFAULT_HTTP_TIMEOUT`
`TOSCA_CLIENT_HTTP_TIMEOUT`	HTTP timeout for communications to Tosca servers only.	`DEFAULT_HTTP_TIMEOUT`
`JIRA_CLIENT_HTTP_TIMEOUT`	HTTP timeout for communications to Jira servers only. This is the same for both Jira Data Center and Jira Cloud.	`DEFAULT_HTTP_TIMEOUT`
`BEARER_CLIENT_HTTP_TIMEOUT`	HTTP timeout for authenticating to certain systems.	`DEFAULT_HTTP_TIMEOUT`
`TOKEN_CLIENT_HTTP_TIMEOUT`	HTTP timeout for authenticating to certain systems.	`DEFAULT_HTTP_TIMEOUT`
`INTERMODULE_CLIENT_HTTP_TIMEOUT`	HTTP timeout for communications between Vera modules.	`DEFAULT_HTTP_TIMEOUT`
`WEBHOOK_PROVIDER_HTTP_TIMEOUT`	HTTP timeout for internal Vera communications.	`DEFAULT_HTTP_TIMEOUT`
`SERVER_STATUS_HTTP_TIMEOUT`	Internal Use Only	`DEFAULT_HTTP_TIMEOUT`