related actions and record actions in record, is there any limit?

I do not know of a documented limit. What do you plan for?

The question is, if it is useful from a certain point to have huge numbers accessible for every user. Related actions can be hidden/shown depending on the showWhen conditions of the related actions

I think it would be unusual for a large number of related actions to be concurrently visible for a given user for any given state of a record. Yes, it's possible but usually we design the related actions as proxies for "the next thing a User needs to do". Usually (but not always) there is one required next thing for them to do. There maybe any number of other "elective" things you can do (e.g. 'Cancel this Order' which could come at any time during an order fulfilment process). What I have done in the past is to segregate the 'required' "Next Action(s)" from the 'elective' "Action(s)" so that they're not all in one menu list.

"the next thing a User needs to do"
i have a different mindset on that.
It feels like overthinking related actions.
reason: A related action triggers an action, which should be performed for that specific item. not necessarily for that item. usually embedded in certain business contexts which makes sense, but its not necessarily the next step in line as it can be something like "add note", "reopen case", "lock case", "change case assignment" etc. 

I get what you're saying...some of your examples are exactly what I tried to illustrate - elective/optional actions. So I place those separate from the ones that are key to pushing a case to a conclusion which I see is a lot of what applications I have worked on are used for.

I have not seen any limits here posted, and we have one Record that just crossed to 101 Related Actions and all is operating fine.

My use case is unique, back in the day when we converted from the OLD Portal environment to Tempo (our system has been running since 2007), Sites were not as robust yet so we transitioned by creating an Applications record with a listing of each app available in our system.  All Related Actions for these applications themselves are added under the parent Applications Record and only visible when viewing that application.

I have a record with >60 related actions configured (though any one user usually only sees a small handfull).  It works fine for the users, but the record type takes maybe 10 or 20 seconds to open from the design side, and just as long to then switch over to the related actions configuration page.

Hi Chris,How many users use this application? how was application performing?