Skip to content
Discussion options

You must be logged in to vote

After that, you can do:

Sidequest.job.cancel(jobId)

This won't actually delete the job, just cancel it and prevent its execution, or abort it if it's running.
Then it's considered a completed job, thus it will be cleaned based on your cleanup config.

In hindsight, we should have done a delete function, but that would require some lifecycle assertions to do it.

Replies: 3 comments 2 replies

Comment options

You must be logged in to vote
2 replies
@drewbaker
Comment options

@GiovaniGuizzo
Comment options

Answer selected by drewbaker
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants