Bug: AutoTrigger stops working sometimes

[drpdishant]

📜 Description

It happens randomly that the autotrigger doesn't work when developers push a new commit. Reason for this is unknown but autotrigger is executed for all the pending commits if we recreate the pods in devtroncd namespace.

👟 Reproduction steps

No such steps for reproduction. I am not sure whether others are facing the issue, but need to understand where can we observe the logs for any errors.

👍 Expected behavior

Autotrigger should run indefinitely for all the new commits for the configured branch.

👎 Actual Behavior

If you observe the commite timestamp and autotrigger time you see there's a big difference.
And that too was triggered when I restarted all the pods in devtron namespace.

There's another issue which is also related devtron service that led me to abort the manually created builds in between. I'll raise it separately.

☸ Kubernetes version

EKS 1.28

Cloud provider

AWS

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

AB#9290

[abhibhaw]

This has been fixed in our recent release, feel free to reopen if you still encounter this issue