So you decided to use gnosis safe and its multisig for your smart contracts. Great decision if you moved from EOA and one private key to more secure setup.

With that there are some caveats and experiences you need to prepare for.
Strongly recommend that you first do some actions and signings of transactions on testnet, better yet, try to do exact same actions on testnet you plan to do on mainnet.
Reason is that you might come into unexpected problems that are better experienced on testnet first.

So what are they, they will probably be associated with transaction builder and Safe UX. Its a tool that tries to build transactions for you and should be ok but the actual transactions might be wrongly configured and make you stuck.
So here is what could go wrong:

1. You can try to make transaction that will fail, Safe will make some simulations, maybe even recommend that it will fail but you would still try to make it, what then usually happens is that trx is made with low or 0 gas settings and you will make trx in interface but it will never go through, making your UI stuck and you will need to replace that trx.

2. Replacing can also have its problems, for example, builder might give you wrong or too low gas and wrong NONCE, which is picked from the wallet for creator, so it could be that particular installation of wallet has not made any trx and you did make them on other device, safe would pick up nonce from it which is wrong and you will get nonce 2 but actual nonce should be 14 (you need to see what is actual number of transactions that multisig smart contract wallet had). In that case you need to write it yourself and add proper value, otherwise it will also be stuck and your UI will be processing this forever and you will again need to try to make proper trx that will “kill” this one.

3. Processing and indexing problems, the Safe UI and the whole FE sometimes is lagging behind (said by their support) so even if you are using some chain that is not congested, you will need to wait for trx to appear. I had situation where trx was ok but indexing of their FE was lagging and they said that it can lag like that up to an hour. So all I can do was wait. It was bit faster, but not much something like 45 mins, on other occasion I waited some 10 minutes, all on chain that is more empty then full.
   
   So take this into account when using Safe and prepare for all of this and try things out.

So you decided to use gnosis safe and its multisig for your smart contracts. Great decision if you moved from EOA and one private key to more secure setup.

With that there are some caveats and experiences you need to prepare for.
Strongly recommend that you first do some actions and signings of transactions on testnet, better yet, try to do exact same actions on testnet you plan to do on mainnet.
Reason is that you might come into unexpected problems that are better experienced on testnet first.

So what are they, they will probably be associated with transaction builder and Safe UX. Its a tool that tries to build transactions for you and should be ok but the actual transactions might be wrongly configured and make you stuck.
So here is what could go wrong:

1. You can try to make transaction that will fail, Safe will make some simulations, maybe even recommend that it will fail but you would still try to make it, what then usually happens is that trx is made with low or 0 gas settings and you will make trx in interface but it will never go through, making your UI stuck and you will need to replace that trx.

2. Replacing can also have its problems, for example, builder might give you wrong or too low gas and wrong NONCE, which is picked from the wallet for creator, so it could be that particular installation of wallet has not made any trx and you did make them on other device, safe would pick up nonce from it which is wrong and you will get nonce 2 but actual nonce should be 14 (you need to see what is actual number of transactions that multisig smart contract wallet had). In that case you need to write it yourself and add proper value, otherwise it will also be stuck and your UI will be processing this forever and you will again need to try to make proper trx that will “kill” this one.

3. Processing and indexing problems, the Safe UI and the whole FE sometimes is lagging behind (said by their support) so even if you are using some chain that is not congested, you will need to wait for trx to appear. I had situation where trx was ok but indexing of their FE was lagging and they said that it can lag like that up to an hour. So all I can do was wait. It was bit faster, but not much something like 45 mins, on other occasion I waited some 10 minutes, all on chain that is more empty then full.
   
   So take this into account when using Safe and prepare for all of this and try things out.