I was imaging an object in the last few days and I set the meridan flip in the new location in the mount tab from where it used to be in the imaging section. Long story short the meridan flip simply didn't happen, it sat there doing nothing.

I set it to do the flip at "0.05" in the setting in the mount tab. So at at that time it certainly started the process, it just didn't move the mount at all.

There were four log files EKOS created on the night and I think I've attached the right one attached. I've not had too many issues with meridan flips previously from version v2.9.8, v3.2.3 etc. So this seems new to version 3.3.1.

I'm using StellarMate that is updated to v3.3.1 and the same version on the Mac as well. Hopefully the logs uncovered the bug or what I have configured incorrectly.

That's pretty close to the meridian, less than a degree, and perhaps the mount thinks that it hasn't crossed the meridian. I would try 0.1 hours as a minimum and maybe more if you mount can track significantly past the meridian.

Something that migt help in Ekos would be to retry the flip if it doesn't hppen at the preordained time. This requires that you know which side of the pier the mount thinks it is on.

When I understand it right, your scope was pointing to RA 16:25:15. I just tried to reconstruct your situation with KStars using Brisbane as location. There this target has transit time around 21:10. Your log starts at 22:10, so the target has already passed the meridian.

Maybe these is the wrong log file.

What text should I be searching for in the log files so I can hunt down the right one do you know?
The meridan flip definitely failed and I'd like to see if we can figure out why.