You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/sdk/intervaltrigger.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ description: "`intervalTrigger()` is set as a [Job's trigger](/sdk/job) to trigg
12
12
Intervals are set with a number of seconds. There are some important considerations:
13
13
14
14
- The Job will first run the specified number of seconds after it has first connected to an [Environment](/documentation/concepts/environments-endpoints). This will happen when you first [deploy](/documentation/guides/deployment) that Job.
15
-
- The minimum interval is 60 seconds (any input less than this it will default to 60).
15
+
- The minimum interval is 20 seconds (any input less than this it will default to 20).
16
16
- The maximum interval is 2_592_000 seconds (30 days), if you pass more than this it will trigger every 30 days.
17
17
18
18
If you wish to Run a Job at an exact time or less frequently than once pr day you should use a [cronTrigger()](/sdk/crontrigger) instead.
0 commit comments