The discussion highlights the balance between storing workflow state and utilizing external databases, emphasizing that workflows can run indefinitely with proper management. A unique mechanism called "continuous new" allows for resetting workflow history while ensuring code upgrades remain feasible. This approach addresses the challenges of unbounded history growth and facilitates efficient state management in long-running workflows.