# Self hosted gitlab can not process follow up push **URL:** \ **Category:** Bug Reports\ **Tags:** bugbot\ **Created:** [December 16, 2025, 11:00am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438 "2025-12-16T11:00:45Z")\ **Posts on this page:** 19\ **Page:** 1
**Author:** ![Yuan\_Gao](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuan_gao/32/91318_2.png) [@Yuan\_Gao](https://forum.cursor.com/u/Yuan_Gao)\ **Post date:** [December 16, 2025, 11:00am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/1 "2025-12-16T11:00:46Z")
### Where does the bug appear (feature/product)? BugBot ### Describe the Bug We setup the self hosted gitlab connection with cursor, then created an MR to trigger the bugbot review, the bugbot created several comments, everything works fine. Then we try to resolve the comments, pushes more fixes, from here, bugbot seems to be stuck, no more actions shown in the MR page. I tried to trigger the bot manual by the command: “cursor review verbose=true”, I only got one message as below ```auto Bugbot request id: serverGenReqId_56aab9f5-cb89-421d-9a24-1072826c758d ``` Then there is no any other messages, seems like a server stuck, or some exceptions happened, the process got interrupt. Also noted, we didn’t set the `automatically run only once` feature, the switch is off for that, both for gitlab config and user config, this switch is off. And the manual triggered run is not working, prove that this is not a regular config issue. And the first push triggered bugbot and the comments are successfully posted prove that the connection between self hosted gitlab and cursor is all good, so I think this should be a server bug. ### Steps to Reproduce 1. create a MR in self hosted gitlab 2. wait for bugbot to review 3. resolve the comment and push new commits 4. there is no more actions from bugbot ### Expected Behavior the bugbot continue working. ### Operating System MacOS ### Current Cursor Version (Menu → About Cursor → Copy) this is a bugbot issue, no cursor version ### For AI issues: add Request ID with privacy disabled Bugbot request id: serverGenReqId\_56aab9f5-cb89-421d-9a24-1072826c758d ### Does this stop you from using Cursor Yes - Cursor is unusable ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [December 16, 2025, 11:53am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/2 "2025-12-16T11:53:01Z")
Hey, thanks for the detailed report. Looks like an issue with handling webhook events from self-hosted GitLab after the first review. Thanks for the Request ID - I’ll pass it to the engineers. Can you check the following: 1. In your GitLab project settings - Settings \> Webhooks \> check the Cursor webhook. Are there errors in Recent Deliveries? 2. In webhook settings, check which events are enabled - Push events and Merge request events should be on. 3. After a new commit - does a new webhook delivery appear in GitLab logs? This will help us figure out where the connection breaks. I’ll pass the Request ID to the team - they’ll check logs on our side. ---
**Author:** ![Yuan\_Gao](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuan_gao/32/91318_2.png) [@Yuan\_Gao](https://forum.cursor.com/u/Yuan_Gao)\ **Post date:** [December 16, 2025, 12:06pm UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/3 "2025-12-16T12:06:51Z")
Thanks for your reply, seems like we do not have a page showing the deliveries results, but I believe the delivery is success since when we run `cursor review verbose=true`, we do see a response from cursor bot with a resuqest id, so that id might be a good start for cursor team to investigate? Then here is the screenshot of the webhook config for the cursor bugbot ![image](https://us1.discourse-cdn.com/cursor1/original/3X/e/c/ec3aaa12a8d6318fc981fcc9ba9c9761938a05ee.png) ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [December 16, 2025, 4:01pm UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/4 "2025-12-16T16:01:10Z")
Thanks for the info. If there’s no “Recent Deliveries” page in GitLab, we can check via server logs: 1. On your self-hosted GitLab, can you check the webhook logs in `/var/log/gitlab/gitlab-rails/production.log`? Look for entries right after your follow-up push. 2. Alternatively, in the webhook settings there’s a “Test” button. Try Test \> Push events. Do you get a response from Cursor? 3. You can try creating a new MR with a single commit. Does the first review trigger? This helps confirm if the issue is only with follow-up pushes or with all new MRs. ---
**Author:** ![Yuan\_Gao](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuan_gao/32/91318_2.png) [@Yuan\_Gao](https://forum.cursor.com/u/Yuan_Gao)\ **Post date:** [December 17, 2025, 2:01am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/5 "2025-12-17T02:01:37Z")
I tried with the 2nd instruction, and I got the response 200, so the connection is good. ![image](https://us1.discourse-cdn.com/cursor1/original/3X/3/2/32e6c80489c9166d3f972c07898c159d7d512791.png) 1. I am pretty sure that the new MRs will always trigger the review, but follow-up pushes does not. We have several new MRs triggered the review, although our devs resolved the issues and pushed new commit, and even merged the MR, there is no updates on the cursor admin panel. Here is the screenshot you can check. ![image](https://us1.discourse-cdn.com/cursor1/original/3X/3/e/3e0f621f25b6d53bb7566f41ba885b88b33d245d.png) ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [December 17, 2025, 5:59pm UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/6 "2025-12-17T17:59:42Z")
Thanks for the info. The webhook is connected correctly (HTTP 200 on test), and the issue is confirmed: new MRs trigger reviews, but follow-up pushes are not processed. This seems like a bug in handling webhook events from self-hosted GitLab after the first review. ---
**Author:** ![Yuan\_Gao](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuan_gao/32/91318_2.png) [@Yuan\_Gao](https://forum.cursor.com/u/Yuan_Gao)\ **Post date:** [December 18, 2025, 2:36am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/8 "2025-12-18T02:36:32Z")
Is there an estimated fix time for this issue? ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [December 21, 2025, 11:23am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/9 "2025-12-21T11:23:28Z")
I’ve already shared this with the team, and they’re looking into it. Unfortunately, I can’t provide an exact ETA for a fix yet. ---
**Author:** ![Yuan\_Gao](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuan_gao/32/91318_2.png) [@Yuan\_Gao](https://forum.cursor.com/u/Yuan_Gao)\ **Post date:** [December 22, 2025, 2:00am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/10 "2025-12-22T02:00:31Z")
Got it, please keep me updated, thanks. Looking forward for the fix. ---
**Author:** ![Yuan\_Gao](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuan_gao/32/91318_2.png) [@Yuan\_Gao](https://forum.cursor.com/u/Yuan_Gao)\ **Post date:** [December 29, 2025, 10:40am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/11 "2025-12-29T10:40:17Z")
1 week has passed, is there any updates on this issue? ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [December 29, 2025, 12:25pm UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/12 "2025-12-29T12:25:00Z")
Thanks for your patience. The team is aware of the issue and is working on a fix. Unfortunately, I can’t share an exact timeline yet. I’ll update the thread as soon as there’s progress. ---
**Author:** ![Yuan\_Gao](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuan_gao/32/91318_2.png) [@Yuan\_Gao](https://forum.cursor.com/u/Yuan_Gao)\ **Post date:** [December 30, 2025, 12:29pm UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/13 "2025-12-30T12:29:13Z")
Totally understand, looking forward to your updates. ---
**Author:** ![Yuan\_Gao](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuan_gao/32/91318_2.png) [@Yuan\_Gao](https://forum.cursor.com/u/Yuan_Gao)\ **Post date:** [January 6, 2026, 2:59am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/14 "2026-01-06T02:59:13Z")
Another week passed, any updates on this issue? ---
**Author:** ![Matt\_Ruhlin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/matt_ruhlin/32/79817_2.png) [@Matt\_Ruhlin](https://forum.cursor.com/u/Matt_Ruhlin)\ **Post date:** [January 8, 2026, 10:39pm UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/15 "2026-01-08T22:39:50Z")
Hi all, our team is still looking into this! @Yuan_Gao are you able to provide another recent example request ID by any chance? ---
**Author:** ![Yuan\_Gao](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuan_gao/32/91318_2.png) [@Yuan\_Gao](https://forum.cursor.com/u/Yuan_Gao)\ **Post date:** [January 9, 2026, 2:39am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/16 "2026-01-09T02:39:16Z")
Here you are: Bugbot request id: serverGenReqId\_ba485da8-48f0-4736-b00b-d9bb5fc2170b ---
**Author:** ![Yuan\_Gao](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yuan_gao/32/91318_2.png) [@Yuan\_Gao](https://forum.cursor.com/u/Yuan_Gao)\ **Post date:** [January 9, 2026, 2:51am UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/17 "2026-01-09T02:51:38Z")
The request of the request id provided above does work correctly, so this bug is fixed? ---
**Author:** ![Matt\_Ruhlin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/matt_ruhlin/32/79817_2.png) [@Matt\_Ruhlin](https://forum.cursor.com/u/Matt_Ruhlin)\ **Post date:** [January 9, 2026, 2:47pm UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/18 "2026-01-09T14:47:31Z")
Interesting - glad to hear! We haven’t been able to reproduce the reported issue with our own Gitlab setup, so if everything is working well on your end, this is likely resolved. Let us know if this crops up again and we’ll take another look. ---
**Author:** ![Rao\_Athar](https://avatars.discourse-cdn.com/v4/letter/r/e79b87/32.png) [@Rao\_Athar](https://forum.cursor.com/u/Rao_Athar)\ **Post date:** [January 9, 2026, 2:54pm UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/19 "2026-01-09T14:54:41Z")
That is very frustrating when the bot locks up after the initial run. Since the initial connection and review worked, I believe the issue is a server-side state lock related to that specific Merge Request ID after the first successful execution. I suggest checking two things: first, confirm in your self-hosted GitLab configuration that the push event webhook is successfully firing upon subsequent commits. Second, if the webhooks look correct, the BugBot server logs associated with that request ID should show where the process is exiting or why it is not picking up the queue item. It is likely getting interrupted due to a failed state check. Hope this helps! ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [January 31, 2026, 2:55pm UTC](https://forum.cursor.com/t/self-hosted-gitlab-can-not-process-follow-up-push/146438/20 "2026-01-31T14:55:11Z")
Closed on January 31, 2026, 2:55pm UTC This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.