You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Continuing the conversation from the topic covered in #31720, we successfully managed the cancellation resulting from trigger timeout within pull request #31757. Within the same pull request, a generic cancellation log was introduced. This log, however, also surfaces during instances where the trigger completes successfully. To address this matter, pull request #33874 is in progress, aiming to eliminate this generalized trigger log. This alteration is prompted by user feedback, revealing that the presence of the general log caused confusion by implying errors even in cases of successful triggers.
In accordance with the deliberations in issue #31720, it is necessary for us to implement a system that facilitates the communication of pertinent causes for diverse trigger cancellation scenarios. And we need to then incorporate logic designed to convey specific cancellation explanations and subsequently record corresponding detailed cancellation logs.
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
Activity
boring-cyborg commentedon Aug 29, 2023
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
RNHTTR commentedon Nov 27, 2023
Closed by #33874