Update 03_consul.mdx

genesiscommunitysuccess · Jun 13, 2024 · f5220d0 · f5220d0
1 parent 67f3c6c
commit f5220d0
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/06_operations/04_clustering/03_consul.mdx b/docs/06_operations/04_clustering/03_consul.mdx
@@ -82,7 +82,7 @@ systemDefinition {
 
 ### Request fails with 5xx when trying to reach a process that no longer exists
 
-Scenario: This might happen when a resource is moved from one process to another. For example, a `requestReply` originally served from `Service A` is now moved to `Service B`, but consul still holds a reference that is being served by the former.
+Scenario: This might happen when a resource is moved from one process to another. For example, a `requestReply` originally served from `REQ_REP_SERVICE_A` is now moved to `REQ_REP_SERVICE_B`, but consul still holds a reference that is being served by the former.
 
 Solution: Check the consul console (or cli) to see if there is still a resourceMap (under KeyValues) for the process that no longer exists. If there is, [delete it](https://developer.hashicorp.com/consul/docs/dynamic-app-config/kv/store#delete-data). Then restart the Genesis services.