[12.x] Fix incorrect default retry info in Horizon docs #10750
Merged
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a small misleading detail about how Horizon handles retries when the
$tries
option is omitted. In such cases, Horizon retries indefinitely, as opposed to the current docs which state it defaults to 1.You can test this easily by:
$tries
optionhandle()
methodYou will see that the job is retried indefinitely instead of being marked as failed after the first attempt.
For reference, here is where the default value is defined if no tries are set: