Yes, this is always the best course of action, regardless if you’re running our apps or not. We have talked and blogged and even tweeted about this necessaity.
According to the description a rebuild was probably suggested due to a major database issue detected while opening the database but depending on the issue rebuilding might not help. Did DEVONthink or the computer crash/freeze lately?
The first database orphaned all my data and so I went back to an old archive file.
The second database lost all data and did not create any orphaned files
The first database archive functions fine (from Jan 12, 2020)
The second database archive is giving the errors sent earlier in this thread (from Jan 24, 2020). Due to these errors, an archive copy of the database cannot be generated.
I will back up every day now (or archive) but for now, DevonThink Rebuild functionality wiped out two of my very large databases
Also, doing a weekly File > Verify & Repair(or bi-weekly, if you’re not a heavy user of a database) is a good idea. Just to keep up on the general health of your databases.