33186865953
89%

Ran 28 Aug 2026 03:48PM UTC

Jobs 2

Files 31

Run time 1min

Badge

Embed ▾

Committed 28 Aug 2026 03:47PM UTC coverage: 88.558% (-0.07%) from 88.629%

Build # 33186865953

Build Type

push

github

Committed by

pashagolub

Commit Message

[*] document NULL schedule behavior, fixes #833

A job with `job_schedule => NULL` (`chain.run_at IS NULL`) is started at
every scheduler loop tick — every 60 seconds by default. This has
been the behavior since the first release but was never documented
(#833). No behavior change.

- README: example in the add_job() block
- docs/reference-commands-tasks-chains.md: run_at field
- docs/database_schema.md: job_schedule parameter
- docs/how-to-schedule-common-jobs.md: example #6
- docs/explanation-scheduling-model.md: Chain level

Coverage Stats

2500 of 2823 relevant lines covered (88.56%)

1.02 hits per line

Coverage Regressions

Lines	Coverage	∆	File
2	84.68	-1.8%	internal/pgengine/log_hook.go

Jobs

ID	Job ID	Ran	Files	Coverage
1	windows - 33186865953.1	28 Aug 2026 03:48PM UTC	3	66.31	GitHub Action Run
2	linux - 33186865953.2	28 Aug 2026 03:50PM UTC	29	89.62	GitHub Action Run

cybertec-postgresql / pg_timetable / 33186865953
89%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Coverage Regressions

Jobs

Source Files on build 33186865953

cybertec-postgresql / pg_timetable / 33186865953 89%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Coverage Regressions

Jobs

Source Files on build 33186865953

cybertec-postgresql / pg_timetable / 33186865953
89%

README BADGES
x