I undid multiple commands - won't redo back

[gnarkill283]

I undid multiple commands to see something I accidentally deleted and made sure not to touch or zoom anything. I then redid a number of commands until it stopped letting me saying there's nothing to undo but I hadn't reached the point where I started undoing. Why?!

[gnarkill283]

saying there's nothing to redo*

[john.vellek]

Hi @gnarkill283,

Did you use the U or Undo command?  Here is a description of UNDO.

Please select the Accept as Solution button if my post fully solves your issue or answers your question.

[RobDraw]

If you had saved before doing multiple undos, it wouldn't have been an issue.

Also, in this particular case, wanting to see what you had last deleted, you could have used the OOPS command.

[dbroad]

An alternative to using undo or u is to use oops instead.  It will unerase the last set of items deleted without otherwise undoing your work.

Sounds like you might be confusing undo, redo, and mredo.  If you are using the ribbon, you may be using mredo.  Redo and mredo are very finicky as you seem to be aware of.  Any command issued between an undo and mredo will interfere with being able to redo forward to the point you began undoing.  Just remember to oops instead.

[gnarkill283]

I shouldn't have said that I accidentally deleted something. What really happened and it happens a lot is that I delete something with information that I need to input into a new tag or whatever. So after making many changes, I'll realize I need that information so I will undo to see it and redo back to enter it in. I literally do nothing else but press ctrl-z to back up to that info and ctrl-y to get back to where I was and it won't always go back. I am not zooming or touching anything. It doesn't make any sense and is worrisome. I guess if it happens again, I will track exactly where it messes up.

[RobDraw]

Since you have learned that it is risky to do what you did, I would hope that you save your work before undoing a bunch of steps, knowing that you will need to redo.

Lesson learned?

[dbroad]

If @RobDraw hasn't solved your problem, then use CTRL+X to erase what you might need again and CTRL+V to paste it back when you need it.

[gnarkill283 · Accepted solution]

Thanks but so far I haven't been able to replicate the problem so who knows what happened. What I was looking for was someone knowing if there is a limit to how many undos or redos you could do or if there are any settings that limit the memory used to store undos and redos like other programs. I can't seem to find any settings like that. Also I found out you can't undo or redo through a edit xref in place.

[RobDraw]

So, in the future, you're not going to rely on undo/redo for multiple steps, right?

[Stephen_DavisAF8XY]

You guys are super snooty. The fact that the undo icon at the top of the program is the fastest and most easily grabbed edit, it should possibly not be one of the most permanent edits to the project. Seems likely that if the oops command is so easy to rectify, maybe it should have the fastest/easiest button in the program, and one might have to dig for a more permanent solution.

The horses are high on this thread...

[RobRocks]

---

@Stephen_DavisAF8XY wrote:

The horses are high on this thread...

---

And you just joined the herd.

---

@Stephen_DavisAF8XY wrote:

one might have to dig for a more permanent solution.

---

You don't need need to dig. Just start using "best practices".

[dbroad]

@Stephen_DavisAF8XY Thanks for completely wasting my time by replying to an 8 year old thread with no new information.

[pendean]

@Stephen_DavisAF8XY Tell Autodesk all about it to fix it as you see fit if you are serious
https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Feedback-to-Autode... 

Best wishes.

[clp]

CTRL Z & CTRL Y worked in 2023, doesn't work in 2024.  Will probably work in 2027.  It just comes and goes.  CAD comments are the absolute the worst.  One expects professional courtesy, half a century of experience, the true wisdom of the elders, alas...  high horses and all.  Good luck.  

[RSomppi]

---

@clp wrote:

CTRL Z & CTRL Y worked in 2023, doesn't work in 2024.  Will probably work in 2027. 

---

What about '25 and '26?

[clp]

I'm using 2026 now and it doesn't work for me.  6 month old PC, Windows 11, i9, T1000,  64GB,
2025 did work, but it was a different computer.  ¯\_(ツ)_/¯

[RSomppi]

That was a rhetorical question meant to point out that there was a gap in your analysis of a completely different issue than the topic of this thread.

[clp]

\_(ツ)_/¯