Replies: 1 comment
-
This was implemented 🥳 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently there are 3 ways of triggering a job run:
We've had multiple requests for a way to manually invoke a job, passing in a payload, and getting back a single run. This would work similarly to how our job test service works, but work via API and within another run.
Invoke Trigger
Jobs that can be manually invoked will use a new Trigger called
invokeTrigger
. This will work similarly toeventTrigger
but won't have an event name:Now that job can be manually invoked using a reference to the
Job
instance:Another benefit of having this manually invokable jobs is it would make it much more ergonomic to use with the useRunDetails React hook.
Implementation
This could work similarly to the
TestJobService
, where an event is created and then immediately used to create a new run, instead of going through theEventDispatcher
system. The name of the event could be the job id, and theid
of the event would either be randomly generated on the server, or the invocation task idempotency key when invoked from inside another job run.Beta Was this translation helpful? Give feedback.
All reactions