CapacityLimitExceeded + NoCapacitiesInRegion after stuck system session — 24hr outage on F64 France

Sorry to hear that, can you check rapidely on utilization if you exceed 100% here : 

There is currently no "reset button" for the 24-hour smoothing window. It's based on a burst and smoothing system on the capacity, so If you consumed 500% of your capacity in one hour, that debt must be "paid back" over the following 24 hours (smoothing).

You can also use Surge Protections to limit the usage of background operations and have at least a minimum of capacity for Interactive Operations.

For the rest of your questions, I don't have all answers but a best practices on Production is to have separate capacities : if you identify 2 or 3 specific items (reports, notebooks or warehouse) that are using a lot of CU, consider a mutli-capacity architecture. Instead of running everything on a single F64, you can provide a smaller, secondary capacity for the data processing parts : data ingestion (pipelines, dataflow gen2...), spark notebook... So you can have your Production Warehouse and reporting on the F64 remain responsive and unaffected.

Hope it can help you ! 

Best regards,

Antoine