Replies: 1 comment
-
It sounds like you should run an INSERT..SELECT command
…On Thu, May 11, 2023 at 12:58 AM pulpdood ***@***.***> wrote:
This may sound like an anti-pattern or odd request, but the situation we
have is that a part of our code had created jobs which were run and marked
as completed, but without performing the task we want because the job
handler code logic was incorrect.
We have since updated the job handler code, and we want to re-run the
previously mentioned jobs on the new job handler code, but unfortunately
the jobs are now in the archive table, and we're not sure how to re-trigger
these jobs to run.
—
Reply to this email directly, view it on GitHub
<#392>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFAMTV646AKRWZGZLB4HTDXFR5ZJANCNFSM6AAAAAAX5TVBGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
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
-
This may sound like an anti-pattern or odd request, but the situation we have is that a part of our code had created jobs which were run and marked as completed, but without performing the task we want because the job handler code logic was incorrect.
We have since updated the job handler code, and we want to re-run the previously mentioned jobs on the new job handler code, but unfortunately the jobs are now in the archive table, and we're not sure how to re-trigger these jobs to run.
Beta Was this translation helpful? Give feedback.
All reactions