Your transaction has likely been purged, if you’re checking it on mempool.space it can be a bit misleading as it shows about 1GB of mempool transactions, whereas the default configuration for nodes is 300MB. It’s possible if you do an SPV resync in bisq you’ll find that your funds show as available again and you’ll be able to send with a higher fee.
Failing that you can attempt a child pays for parent transaction, if you control the receiving address of where the funds were sent you’ll be able to simply send them on with a higher fee (even to another one of your addresses), and the fee will average out over both transactions, or if there was a change output in bisq then you can also send that on with a higher fee. It’s based on sats/vByte so if your initial transaction had a large number of inputs and/or outputs you’ll need a higher fee on the second transaction to bump the average fee up.
this is the funny part, i did a resync and both transactions show still as pending.
ok i need to read up on child pays for parent. Am i right in understanding it in following way: sending from adddress a to address b. Before it confirms, i create transaction from address b to address c with high enough fee to cover both?
Also weird thing is that it doesnt even show up as pending on the recieveing end…(lnd on-chain wallet).
Am i right in understanding it in following way: sending from address a to address b. Before it confirms, i create transaction from address b to address c with high enough fee to cover both?
Yes pretty much. Send with a higher fee than the current recommended fees (maybe x3 higher) as the weight of the deposit transaction will be more than a simple B to C transaction.