/intake says an initiative cannot be found | Wrong initiative ID or wrong Slack workspace/team. | Run /intake status ENG-123 with the exact ID shown in inrelay. |
| inrelay asks for more context | Quality check found coverage gaps, conflicts, weak source material, open readiness questions, or a PRD section is marked as a gap. | Answer readiness questions, fill the PRD section gap, mark it not applicable with a reason, or add more Slack, email, or file context. |
| A small bug or patch did not use the low-risk lane | The initiative is not bug or patch, is larger than s, has missing lightweight brief fields, has hard pre-flight signals, has stale or ambiguous repo evidence, touches multiple repos, or matches a high-risk category such as security, auth, billing, data loss, platform-wide, or multi-system work. | Continue through the normal PRD flow or add the missing context. Do not split broad or risky work only to force low-risk routing. |
| No discovery thread appears after approval | inrelay does not know a Slack channel or Slack delivery failed. | Approve from a Slack channel, configure a team, notification, or discovery channel, or check Slack installation. |
| A code-inferred discovery answer is not auto-applied | The answer is not low-risk, not code-answerable, lacks fresh citations, has low confidence, has stale or ambiguous evidence, or would decide product intent, ownership, rollout, support policy, live metrics, or business priority. | Accept or edit the cited proposal if it is correct, or answer the question manually. |
/intake tasks is blocked | The latest PRD is not approved, Technical Discovery is not complete or manually closed, technical context is missing, or the web workflow reports a Delivery Plan blocker. | Complete the listed prerequisite and rerun the command. Linear connection is needed later for Send to Linear, not for draft generation. |
| Send to Linear is blocked | The draft task list is not ready, Linear is disconnected or action-required, or a handoff retry is waiting on a partial failure. | Review the Delivery Plan blockers, reconnect Linear if needed, then retry Send to Linear from the initiative page. |
| GitHub repos do not appear | GitHub is not installed, credentials cannot refresh, or the app lacks repository access. | Reinstall or manage GitHub from Settings > Integrations. |
| GitHub index shows warnings | Repo language, framework, or workspace shape is unsupported, generated/vendor/build/dependency/binary/oversized files were excluded, or the index is stale. | Review the warning and verify implementation details manually. |
| Linear shows action required | OAuth token refresh, webhook setup, or revocation handling needs attention. | Reconnect Linear from Settings > Integrations. |
| Handoff Pack preparation is blocked | Delivery Plan handoff, repository scope confirmation, repo/docs decision, blueprint approval, or no-blueprint eligibility is missing. Automation may also be waiting for GitHub, Linear, repo indexing, or blueprint configuration. | Open the Handoff Pack stage and resolve the listed blockers. If an operation is running, wait for it or use only the recovery action the UI offers. |
| A Handoff Pack First target cannot generate a draft pack | The target is not confirmed or amended, the context snapshot is missing or stale, required source context is absent, or provider validation failed and returned a blocker. | Confirm or amend the target, answer the shown Handoff Pack readiness gaps, refresh context, then regenerate the draft pack. PRD and Delivery Plan gates are not required for this flagged workflow. |
| Handoff Pack First actions are disabled | handoff_pack_first_workflow_enabled is off for the environment, organisation, or team. Existing Handoff Pack First records are read-only from the persisted workflow mode. | Re-enable the rollout flag for the team before making new Handoff Pack First changes, or keep using the classic workflow for new initiatives. Existing packs, approval PRs, publication records, optional artefacts, and download links remain readable. |
| A carried-forward Delivery Plan or repo/docs answer was reopened | inrelay detected a material change to task content, acceptance criteria, dependencies, grouping, repository scope, blueprint scope, inspected evidence, stale index evidence, or a hard repo/docs blocker. | Review the changed target or blocker and answer only the reopened question. Non-material operation or timestamp changes should not reopen signed answers. |
| Handoff Pack publishing is blocked | No prepared packs exist, GitHub write permissions are missing, or the selected destination is unavailable. | Prepare packs first, then check GitHub write upgrade and Handoff Pack publishing settings. |
| Blueprint state looks stale | GitHub webhook delivery may have been missed, or the PR changed outside inrelay. | Use Refresh from GitHub in the advanced recovery controls when a Blueprint PR exists. |
| Blueprint PR needs to be recreated or updated | The current Blueprint PR may be stale or failed, but inrelay only regenerates it when the Blueprint gate allows creation, update, or an approved-scope revision. | Use Regenerate Blueprint PR in the advanced recovery controls when it is visible. Otherwise resolve the shown gate blocker or continue review in GitHub. |
| An operation shows Needs attention | inrelay has not seen healthy progress for queued, running, or retrying work within the expected window. The worker may still finish and update the operation later. | Open the affected stage, review the operation detail, refresh manually, and retry only when the UI offers a safe retry action. |
| Generation is paused by cost cap | Monthly LLM spend reached the configured cap. | Increase the cost cap or wait for the next billing period. |