If you haven’t, report it to , the more people that report it the higher priority it will be to fix it. Yes, it is a bug that they introduced one or two versions ago.
A partial workaround is to break your bitmap up into digestible pieces using this website: http://imagesplitter.net/
This is only a partial fix as it can leave artifacts at the split points.
Contacting support through a forum, and getting a support ticket closed promptly by someone in the company is going to be a new experience for most of us.
Typically the complexity of the file uploaded dictates the processing times. i.e. a NEMA 23 stepper plate (with 5 holes) or a multi-segment file that has A LOT of engravings. From experience, it’s somewhat hard to tell if it’s the file in question or the cloud side post processor. I think they are working on presenting error messages to clue in the end user on why the post processor fell down and go boom.
I’d rather if it had a checksum that guesstimates internally how long it would take to completely process and if it going to take longer then let’s say 5mins throw a message at the end user that it’s going to take a while. Or better yet clue in the user on why it’s going to take while so they go into their vector app of choice and make the appropriate changes.
What I do know, When it does take an enormous about a time to processes it does eventually finish. Usually.