When we have a rule queued and try to abort it, nothing happens. It’s like the abort itself gets placed in the queue… While that is waiting to abort, any new executions (triggers from S3 upload) are still skipped because it sees that aborted run as still in queue. This doesn’t make sense; aborting something should be immediate. I’ve never seen this behavior anywhere else and it’s becoming an issue today.
Hi
When a Rule execution is queued, initiating an Abort is not instantaneous. The Abort request needs to be processed by downstream services before the original execution can be fully cleared.
While the Abort is being processed, the original execution continues to be considered active. Since a Rule can only have one active execution at a time, any new trigger during this period, including an S3 upload, will remain queued until the previous execution has been fully aborted.
Once the Abort is completed and the original execution is marked as Aborted, the existing execution is cleared and the next execution can proceed normally.
So, the behavior you're seeing is due to the time required to complete the Abort rather than the Abort request being permanently queued or ignored.
Thankyou!
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
