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.

Sign up for GitHub

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

Remove a duplicated sentence from define-a-timer-start-event #49

Merged
merged 4 commits into from
Apr 29, 2024
Merged

Remove a duplicated sentence from define-a-timer-start-event #49

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f2cfe63
Update define-a-timer-start-event
rudysap Mar 6, 2024
3c6ae75
Merge branch 'main' into patch-1
Karunaharan Apr 15, 2024
2434733
Merge branch 'main' into patch-1
Karunaharan Apr 29, 2024
a801746
Merge branch 'main' into patch-1
Karunaharan Apr 29, 2024
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 docs/ci/Development/define-a-timer-start-event-ae14ad7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ If you want to configure a process to automatically start and run on a particula
> ### Remember:
> - When you deploy or undeploy an integration flow with *Scheduler*, the system automatically releases all the scheduler locks.
>
> - When you deploy small integration flows with *Timer* \(for example, an integration flow with timer, content modifier and mail adapter\), due to fast processing times, multiple schedules are triggered. When you deploy small integration flows with *Timer* \(for example, an integration flow with timer, content modifier and mail adapter\), due to fast processing times, multiple schedules are triggered.
> - When you deploy small integration flows with *Timer* \(for example, an integration flow with timer, content modifier and mail adapter\), due to fast processing times, multiple schedules are triggered.
>
> - If the *Timer* is configured to trigger message processing at periodic intervals and the processing isn’t completed before the next scheduled interval, then the *Timer* skips the following interval.
>
Expand Down
Loading