Repository navigation
Conversation
revam
added this pull request to stack #1490
October 3, 2026 17:38
harshithmohan
force-pushed
the
split/07-scheduled-actions
branch
from
October 3, 2026 17:43
c845ed8 to
5c5ed6a
Compare
revam
force-pushed
the
split/06-restart-reasons
branch
from
October 3, 2026 18:48
82ef6f6 to
bdf640d
Compare
revam
force-pushed
the
split/07-scheduled-actions
branch
from
October 3, 2026 18:48
5c5ed6a to
073659e
Compare
harshithmohan
force-pushed
the
split/07-scheduled-actions
branch
3 times, most recently
from
October 4, 2026 08:00
e7dfe6a to
72bdf10
Compare
harshithmohan
force-pushed
the
split/06-restart-reasons
branch
from
October 5, 2026 17:38
9fc2f62 to
4a29f31
Compare
harshithmohan
force-pushed
the
split/07-scheduled-actions
branch
from
October 5, 2026 17:38
72bdf10 to
c81a481
Compare
harshithmohan
removed this pull request from stack #1490
October 5, 2026 17:42
harshithmohan
added this pull request to stack #1492
October 5, 2026 17:42
- Listed every scheduled action from `GET Action/Scheduled` by category, with its state and progress, next run, last runs, minimum interval and triggers
- Ran one now through `POST Action/Scheduled/{id}`, asking first when it says so, and cancelled its run through `…/{id}/Cancel`
- Edited the triggers of each type, the queue-cleared one included, saved with `PUT …/{id}/Triggers` and reset with `DELETE …/{id}/Triggers`, showing the server's errors under the trigger they name
- Kept the trigger types in one list, so a new one is one entry, and kept a type it does not know as it is
- Said "Only by hand" for an action without triggers, and named the triggers for one whose triggers have no time, such as start-up
- Fetched the list again every 2 seconds while a run is in the queue, otherwise every 30
harshithmohan
force-pushed
the
split/06-restart-reasons
branch
from
October 6, 2026 13:50
4a29f31 to
8b7270d
Compare
harshithmohan
force-pushed
the
split/07-scheduled-actions
branch
from
October 6, 2026 13:50
c81a481 to
d3a89c8
Compare
harshithmohan
removed this pull request from stack #1492
October 6, 2026 13:53
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
The server runs its recurring work as scheduled actions (
/api/v3/Action/Scheduled), which replaced the frequencies dropped in Part 1. Nothing in the WebUI showed or edited them.What changed
POST …/{id}, asking first when the action says so) and cancel (…/{id}/Cancel).PUT …/{id}/Triggersand reset withDELETE …/{id}/Triggers; the server's errors show under the trigger they name, and an unknown type is kept as it is.Where to look first
src/core/react-query/scheduled-action/helpers.ts: the trigger types and their labels in one list.src/components/Settings/ScheduledActions/TriggerEditor.tsx: editing and validation.src/components/Settings/ScheduledActions/ScheduledActionItem.tsx: one action's row.Feedback wanted
Whether the trigger editor's validation matches the server, and the UX of editing triggers.
Left to do
Quick actions still call the legacy
/api/v3/Action/*routes, most of which just queue the matching scheduled actions; they could start actions directly once the server's generated-UI work is final.Stack
Part 7 of 12 in the split of #1477. Below: Part 6, the restart reasons and the server version bump. Above: Part 8, the TMDB linking fixes.
Testing
pnpm tscheck,pnpm lint,pnpm testandpnpm buildpass at this branch's tip. Manual, on 6.0.0-dev.495: run and cancel an action, add an interval trigger below the minimum (the server's error shows), save and reset.