Trigger scheduled job just by specifying the name of the scheduled job. #185
Conversation
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
|
✅ Valid PR for ActionPack Thank you for your contribution. This PR complies with the CONTRIBUTING.md. |
SapphicFire
approved these changes
Oct 17, 2025
Contributor
SapphicFire
left a comment
SapphicFire
left a comment
There was a problem hiding this comment.
Looks good to me. I appreciate the handling for Global, though we are unlikely to see that scope in execution from this pack
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This update introduces a flexible flow action that enables users to trigger any scheduled job on demand by simply specifying the job name as input.
Additionally, an error-handling step has been implemented to capture and return a clear execution status (Executed or Failed).
If the job name is invalid or an unexpected error occurs during execution, the flow safely returns a "Failed" status instead of throwing runtime errors, ensuring a smooth user experience.
This flow action is lightweight, reusable, and highly practical for automation scenarios, testing purposes, or triggering jobs on the fly without navigating to the Scheduled Jobs module.