google-gemini/gemini-cli · error · OrchestrationError
Issue number is missing in Firestore metadata.
Error message
Issue number is missing in Firestore metadata.
What it means
Error "Issue number is missing in Firestore metadata." thrown in google-gemini/gemini-cli.
Source
Thrown at tools/caretaker-agent/cloudrun/pr-generator/workflow/orchestrator.py:169
self._setup_workspace()
# Load firestore specifications
try:
firestore_doc = self.config.load_and_validate_firestore_doc()
except Exception as e:
raise OrchestrationError(f"Failed to load / validate config: {e}") from e
issue_id = firestore_doc.get("workable_spec", {}).get("issue_id")
github_metadata = firestore_doc.get("github_metadata", {})
issue_num = github_metadata.get("issue_number")
owner = github_metadata.get("owner")
repo = github_metadata.get("repo")
doc_id = self.config.firestore_id or (
f"github_{owner}_{repo}_{issue_num}" if owner and repo and issue_num else None
)
if not issue_num:
raise OrchestrationError("Issue number is missing in Firestore metadata.")
# --- STEP 1, 2, 3: Concurrency Dual-Lock Validation & COMMIT_GENERATION State Update ---
execution_id = self.config.execution_id
logging.info("Validating concurrency dual-lock in Firestore for issue #%s...", issue_num)
claim_action = acquire_lock(
lock_holder=execution_id,
doc_id=doc_id,
owner=owner,
repo=repo,
issue_number=issue_num,
lock_duration_sec=900, # 15 minutes
target_status=IssueStatus.COMMIT_GENERATION.value,
)
if claim_action == ClaimAction.SKIP:
logging.info(
"Lock validation: another worker is working on this issue or issue is in terminal state. Exiting cleanly."
)View on GitHub (pinned to 5024443c72)
When it happens
Trigger: Thrown at tools/caretaker-agent/cloudrun/pr-generator/workflow/orchestrator.py:169 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of google-gemini/gemini-cli@5024443c72 (2026-08-12).
Data as JSON: /api/errors/db7f932e36cc1c08.
Report an issue: GitHub.