Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify the meaning of job retries #3028

Draft
wants to merge 4 commits into
base: latest
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion api/alter_job.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ automatically return to the schedule.
|`job_id`|`INTEGER`|The ID of the job being modified|
|`schedule_interval`|`INTERVAL`|The interval at which the job runs. Defaults to 24 hours|
|`max_runtime`|`INTERVAL`|The maximum amount of time the job is allowed to run by the background worker scheduler before it is stopped|
|`max_retries`|INTEGER|The number of times the job is retried if it fails|
|`max_retries`|INTEGER|The number of times the job is retried if it fails. 0 means no retries, -1 means an infinite number of retries. |
|`retry_period`|`INTERVAL`|The amount of time the scheduler waits between retries of the job on failure|
|`scheduled`|`BOOLEAN`|Returns `true` if the job is executed by the TimescaleDB scheduler|
|`config`|`JSONB`|Job-specific configuration, passed to the function when it runs|
Expand Down
Loading