Initial Cloud Functions edge domain stays stuck on "router_rule_not_found" if first deployment fail

Environment: Appwrite Cloud (Region: sfo / Edge Network *.appwrite.network)
Component: Functions (Git / VCS deployment)

Description

When connecting a Git repository to a Function, if the very first deployment fails during build/compilation, the auto-generated branch domain (e.g. <hash>.appwrite.network, Type: Deployed from main) remains permanently broken on 404 router_rule_not_found, even after subsequent deployments succeed and are marked Active.

Steps to Reproduce:

1. Create an Appwrite function connected to a Git repository.
2. Push a commit that fails to build (e.g. missing dependency or build error).
3. Notice that Appwrite creates an initial domain in the Domains tab (e.g. <hash>.appwrite.network marked as Verified).
4. Fix the code and push a new commit. The build succeeds and the deployment becomes Active.
5. Test the function internally via the Executions tab ("Execute now") -> Returns 200 OK.
6. Visit the original auto-generated domain -> Still returns 404 router_rule_not_found with header x-edge-rule-cache: miss.
7. Add a new domain via + Add domain -> Immediately returns 200 OK with x-edge-rule-cache: hit.

Expected Behavior:

When a new Git deployment succeeds and is marked Active, any existing auto-generated Git branch domain (Deployed from main) should automatically rebind to the active deployment and provision the edge routing rule, rather than remaining orphaned to the initial failed build.

Headers Comparison:

• Original domain (stuck):
  HTTP/2 404
x-edge-rule-cache: miss
{"type":"router_rule_not_found","message":"This page is empty, but you can make it yours.","code":404}

• Newly created domain (working):
  HTTP/2 200 OK
x-edge-rule-cache: hit
x-edge-runtime-cache: hit
x-appwrite-deployment-id: <active-id>