Is there anyway to stop a process flow in the middle and continue it later when a record of a database changes its value at some point?

You could use one of the following techniques:

1. Create an Message (receiving) intermediate event type in place where you want the process to stop. The process will wait until proper message (event) comes. Next implement another process or service to monitor database and connect them by UCA.
2. If you want to expand above scenario with timeout, you could youse event gateway which you can find in process designer on pallet in gateways section. If you drop event gateway on your process diagram by default it creates one message (receive) event and one timer event. Depending which came first process will resume in different path.
3. Finally if you need to process something in parallel to waiting for database status change, alternatively use downstream of an Inclusive Diverging Gateway to resume process after all the active paths completed. Mind that in very complex processes it can make performance impact or even create errors.

Please refer to BAW documentation:

1. Event types / Intermediate event / Message (receiving): https://www.ibm.com/docs/en/baw/23.x?topic=events-event-types
2. Modeling delays, escalations, and timeouts by using timer events / event gateways: https://www.ibm.com/docs/en/baw/23.x?topic=events-modeling-delays-escalations-timeouts
3. Converging and diverging process flows with gateways / Inclusive (OR): https://www.ibm.com/docs/en/baw/24.x?topic=process-converging-diverging-flows