Cannot access/connect to database after it was in sleep mode in Aura

I have noticed this on my free instance in the past as well as our new professional server. The servers sleeps (presumably from lack of activity over the weekend - is there a way to stop it from doing that btw?). I resume the instance and its shown as running but I cannot connect to it in the aura web browser nor can i talk to it anymore through my python scripts. Am I doing something wrong turning it back on or is this a known bug? The only way I could get it to work on when the free version did this was to nuke it from orbit and make a new one. Now with my pro database that I am actually using I don’t want to lose the graph I have built up in it. Any thoughts/help would be appreciated.

Could not perform discovery. No routing servers available. Known routing table: RoutingTable[database=system, expirationTime=0, currentTime=1756142676579, routers=, readers=, writers=]

Hi @dpeterson. Is this on an AuraDB Professional trial instance, or a paid instance? If this for a paid instance, please also see our documentation on this Instance actions - Neo4j Aura. If you still suspect an isssue, log a support ticket within our support portal (a new account must be created).

Professional trial instances have an autopause functionality to reduce wasted resources if no queries are detected on an instance. However, once the instance is resumed you will have full access to query again. If you’re having issues with this, I suggest you reach out to our support team as well.