diff --git a/docs/FORGEJO-CI-CD.md b/docs/FORGEJO-CI-CD.md
index 8b9372f..fb1cc56 100644
--- a/docs/FORGEJO-CI-CD.md
+++ b/docs/FORGEJO-CI-CD.md
@@ -249,13 +249,33 @@ journalctl -u forgejo-runner --no-pager -n 50
 
 # Verificar conectividade
 curl -s https://git.esdrasrenan.com.br/api/healthz
+
+# Se o runner mostrar erro "404 Not Found" apos reinicio do Forgejo:
+systemctl restart forgejo-runner
 ```
 
-### Workflow nao dispara
+### Workflow nao dispara apos push
 
 1. Verificar se o arquivo esta em `.forgejo/workflows/`
 2. Verificar se Actions esta habilitado no repositorio (Settings > Actions)
 3. Verificar se o runner esta online (Settings > Actions > Runners)
+4. **Regenerar hooks do repositorio:**
+   ```bash
+   docker exec -u 1000:1000 $(docker ps -q --filter "name=forgejo_forgejo") \
+     /usr/local/bin/gitea admin regenerate hooks --config /data/gitea/conf/app.ini
+   ```
+
+### Erro de LevelDB Lock (queue nao inicia)
+
+Se o Forgejo mostrar erro `unable to lock level db at /data/gitea/queues/common`:
+
+1. O stack.yml ja usa `FORGEJO__queue__TYPE=channel` para evitar esse problema
+2. Se o erro persistir, limpe o diretorio de queues:
+   ```bash
+   docker exec $(docker ps -q --filter "name=forgejo_forgejo") \
+     rm -rf /data/gitea/queues/*
+   docker service update --force forgejo_forgejo
+   ```
 
 ### Erro de permissao no deploy