config-scheduled-updates-retries

config-scheduled-updates-retries 
[-c value | --configuration=value] 
[-b value | --bootstrap-config=value] 
[-u value | --update-interval-seconds=value] 
[-s <true|false> | --stop-updates-after-repeated-fail-enabled=<true|false>] 
[-f value | --fails-before-stop=value] 
[-o <true|false> | --stop-only-when-cached=<true|false>] 
[-a <true|false> | --always-retry-when-scheduled=<true|false>]
[-d <true|false> | --stop-updates-destination-unavailable=<true|false>]

Overview

Use this command to configure scheduled updates retries following update failures.

Note: The number of retries was previously set by using the stopUpdatesAfterRepeatedFail setting in the Spotfire.Dxp.Worker.Web.config file.

Options


Option	Optional or Required	Default Value	Description
`-c value --configuration=value`	Optional	configuration.xml	The path to the server configuration file.
`-b value --bootstrap-config=value`	Optional	none	The path to the bootstrap configuration file. See Bootstrap.xml file for more information about this file.
`-u value --update-interval-seconds=value`	Optional	60	How often the server checks whether any scheduled updates should be retried. This is set in seconds. Min value is 30, and max value 3600 (one hour).
`-s <true\|false> --stop-updates-after-repeated-fail-enabled=<true\|false>`	Optional	true	Set to "true" to limit the number of times the server tries to update an analysis if the update initially fails. If set to "false", the server will retry the update every `update-interval-seconds` until the analysis is successfully updated.
`-f value --fails-before-stop=value`	Optional	10	Specify the number of times to retry a scheduled update before stopping. Only applies if `stop-updates-after-repeated-fail-enabled` is set to "true".
`-o <true\|false> --stop-only-when-cached=<true\|false>`	Optional	false	If an analysis is not cached and this option is set to "true", the server will retry the scheduled update every `update-interval-seconds` until the analysis is loaded. In this case, the `fails-before-stop` setting is ignored. If set to "false", the server will stop trying to update an analysis as specified in `fails-before-stop`, regardless of whether the analysis is cached. Only applies if `stop-updates-after-repeated-fail-enabled` is set to "true".
`-a <true\|false> --always-retry-when-scheduled=<true\|false>`	Optional	true	Set to "true" to reset the counter for `fails-before-stop` and retry each time the analysis is scheduled to be updated. Only applies if `stop-updates-after-repeated-fail-enabled` is set to "true".
`-d <true\|false> --stop-updates-destination-unavailable=<true\|false>`	Optional	true	Set to "true" to stop retrying on destinations that are offline/unavailable. Only applies if `stop-updates-after-repeated-fail-enabled` is set to "true".