Rerun and cancel of tumbling window trigger immediately get "Failed to rerun/cancel" message.

Konstantin-9879 21

We have tumbling window trigger "A" and tumbling window trigger "B". "B" depends on "A". "A" get failed status because DB was inaccessible some minutes. Now DB is online and we try to invoke rerun of "A", but after rerun we immediately get "Failed to rerun. InternalServerError executing request." message, while other triggers (depended on same DB and failed too) rerun succcessfully. "B" has "Waiting on dependency" state and when we try to cancel it (and remove "A" dependency from "B" after), we immediately get "Failed to cancel" message.
What we can do in this situation? Recreate all dependency graf of all our data pipline from scratch is pain.

MartinJaffer-MSFT 26,061 Reputation points

2021-12-09T22:14:19.557+00:00

Hello @Konstantin-9879 and welcome to Microsoft Q&A. This looks like a particularly tricky and frustrating bug.

I have worked out that the problem must lie in the same layer of code which handles whether dependent triggers should be run or not. Normally, if A failed, B would not even start. So the fact that B is stuck in queue means the handling of A is broken higher up. To further chase down the cause, I would need much more detailed error information on that InternalServerError.

Update: I found some internal resources related to this. The new issue to focus on is the "Failed to cancel" part. That is what I find most concerning.

Just in case I am unable to resolve the "Failed to cancel" part, I would like to have a support case ready to escalate this issue with. If you do not have a support plan, I can provide a 1-time free support ticket. Details on that to follow.
MartinJaffer-MSFT 26,061 Reputation points

2021-12-14T17:02:38.047+00:00

@Konstantin-9879 I haven't received any response or email, so I will assume you found your own solution.

Share via

Rerun and cancel of tumbling window trigger immediately get "Failed to rerun/cancel" message.