Couldnt able to commit the local copy to Mendix cloud!

4
Information dialog opens up and says that – Another operation has been initiated by your team member. Please try again in a few minutes.  
asked
7 answers
4

This message appears when another person in your team is also trying to commit or update to the same branch. It only happens for the branch of your app that is enabled for Mendix Studio (previously, the Web Modeler). To make sure we always have a consistent state, we allow only a single operation at a time. 

In normal circumstances, you wait until the other person is done and then you try to commit or update again and everything is fine.

If something goes wrong, it can happen that the ‘lock’ is not released by Studio Pro and you see this message even if no one else is updating/committing. For these cases, we built a mechanism that releases the lock automatically after some time.

If the problem persists after a quarter of an hour and you know that no else is doing anything to your branch, then it is time to raise a support ticket. 

answered
3

Did it work after a few minutes? If not, you should open a ticket at mendix support.

answered
3

This means someone else of your team is trying to do a deployment. If this happens for a longer time, you need to contact support. This happened from time to time. They should be able to help you.

answered
2

Can’t find anything in Mendix documentation with this specific message but I’m guessing this is what happens when two or more people try and commit/merge/update at the same time. Did you wait a while and try again to the same result?

answered
1

Running into this too. (mx 8.1.1)

any solutions yet?

 

(update)
Once My team mate commited (pressing proceed on the update) the rest of the team could commit again.

It seems like something is locking up, and once that person commits, it seems to get freed up again???

answered
1

Yeah, Raised a ticket to Support team. R&D team identified that one of the commit was in a stuck state and they fixed this. And now it is back to normal. 

If anyone faces the same scenario, please first check with your team mates that some one initiated the commit or not.

 

Approaching the Support team is advisable even when no one from your team has initiated the commit.

answered
0

Same issue here! :-(

Edit: Raised a ticket @ Support

answered