forked from clara-j/media_cleaner
-
-
Notifications
You must be signed in to change notification settings - Fork 6
mumc_configyaml>admin_settings>api_controls>attempts
terrelsa13 edited this page May 13, 2024
·
4 revisions
- Parent
- Description
admin_settings:
api_controls:
attempts: integer
-
There are times when a query either fails to reach the server or the server needs additional time to process prevoius queries
-
The number of times to
attempt
a single API query can be modified here- The delay between original query and the first retry is always 1 second
- This should be enough to resolve most failed initial query attempts
- The delay between original query and the first retry is always 1 second
-
- Delay between the orginal query and retry #1 is (20): 1 second
- Delay between retry #1 and retry #2 is (21): 2 seconds
- Delay between retry #2 and retry #3 is (22): 4 seconds
- Delay between retry #3 and retry #4 is (23): 8 seconds
- Delay between retry #4 and retry #5 is (24): 16 seconds
- Delay between retry #5 and retry #6 is (25): 32 seconds
- ...
- Delay between retry #15 and retry #16 is (215): 32768 seconds
-
0-16 - # of retries
Example:
attempts: 4
- MUMC wiki
- Install
- Files & Directories
- First Run
- Scheduled Run
- Terminology
- Configuration File Examples
- Configuration Tree
-
Additional Information
- OS Permissions
- User And Library Builder
- Played And Created Filter Statement Breakdown
- Played And Created Filter Tag Breakdown
- Dangerous Filter Statements
- Behavioral Statement Breakdown
- Behavioral Tag Breakdown
- Blacklisting vs Whitelisting
- Blacktagging vs Whitetagging
- Library Matching byId vs byPath vs byNetworkPath
- Minimum Episodes vs Minium Played Episodes
- Conditional Behavior Priorities
- Command-Line Options
- Make MUMC Run FASTERRRRRR!!!
- Known Limitations