[Bug] Subgraph doesn't sync after node restart

Bug report

I ran the Graph-Node Docker version locally on my server and deployed the Ethereum subgraph. It works and syncs well. But when I stop the Graph-Node with the docker compose down command and run it again with the docker compose up command, the Graph-Node doesn't continue syncing until I deploy the subgraph again. I've tried it with different RPCs and chains, but I encountered the same problem with all of them. Does anyone have any idea why this happens? Is it normal, or is it a Graph-Node bug?

Edit: I tried to resume the subgraph deployment to fix this problem with the following command:

graphman resume QmUc824r...

and I got:

resuming QmUc824r...
Operation completed

But Nothing happened and the problem remained.
Also, I tried to reassign the deployment using the following command:

graphman reassign QmUc824r... default

and I got:

deployment QmUc824r... is already assigned to default
warning: this is the only deployment assigned to default
are you sure it is spelled correctly?

Again nothing happened and the problem remained.

Edit: Today I noticed that when I ran a graph node for the first time, I saw the line in the logs that has something like this:

Started all assigned subgraphs.

But after restarting it again as I mentioned above, I can't find anything like this in the logs.

Relevant log output

No response

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

• Tick this box if this bug is caused by a regression found in the latest release.
• Tick this box if this bug is specific to the hosted service.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

Linux

Reproduziere das Problem mit dem Graph-Node-Docker-Setup mithilfe von docker compose down und docker compose up und untersuche anschließend die Startprotokolle sowie die im Bericht beschriebenen Befehle graphman resume und reassign. Erledigt ist die Aufgabe, wenn der bereitgestellte Ethereum-Subgraph nach einem Neustart die Synchronisierung ohne erneute Bereitstellung fortsetzt und die Startprotokolle zeigen, dass zugewiesene Subgraphs gestartet wurden.