Skip to content

Commit 33a64b2

Browse files
committed
docs(approvals): a failed read behind a team, position or queue approver refuses the node
Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Utp6CXqXpuVf14Mqo1pznh
1 parent b66d9c6 commit 33a64b2

1 file changed

Lines changed: 23 additions & 9 deletions

File tree

‎content/docs/automation/approvals.mdx‎

Lines changed: 23 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -455,15 +455,29 @@ What an entry that resolves to nobody leaves on the slate depends on its kind:
455455
decide it (the admin-override callout under
456456
[Acting on requests in the console](#acting-on-requests-in-the-console)).
457457
Beside entries that do resolve, a literal is a slot like any other, so a
458-
`behavior` that needs every slot (`unanimous`) waits on it too. A `team`,
459-
`position`, `department` or `org_membership_level` entry whose holder read
460-
failed (`sys_team_member`, `sys_user_position`, `sys_business_unit_member`
461-
or `sys_member`, and for a `department` also the `sys_business_unit` read of
462-
the unit and of its child units) keeps its literal the same way. It logs `could not be
463-
expanded — a directory or read-filter lookup failed` with the `error`,
464-
instead of `expanded to nobody`, and never routes to the holders that
465-
happened to read. An `expression` value whose `resolveAs` read failed keeps
466-
its literal and logs the same line, with the `expression` source.
458+
`behavior` that needs every slot (`unanimous`) waits on it too. A
459+
`department` or `org_membership_level` entry whose holder read failed
460+
(`sys_business_unit_member` or `sys_member`, and for a `department` also the
461+
`sys_business_unit` read of the unit and of its child units) keeps its
462+
literal the same way. It logs `could not be expanded — a directory or
463+
read-filter lookup failed` with the `error`, instead of `expanded to
464+
nobody`, and never routes to the holders that happened to read. An
465+
`expression` value whose `resolveAs: 'department'` read failed keeps its
466+
literal and logs the same line, with the `expression` source.
467+
- **A failed read behind a `team`, `position` or `queue` entry** is not an
468+
empty slate, and the node does not open (ADR-0142 D6). That is a failed
469+
`sys_team_member` or `sys_user_position` read, the `sys_member` read behind a
470+
position, or, for a queue, a failed read of its `sys_queue` row, its
471+
`sys_queue_member` rows or a member table one of its members reads. An
472+
`expression` value resolved as `team` or `position`, and a cross-organization
473+
read filter that fails in front of any of these entries, count the same.
474+
Under every `onEmptyApprovers` value, the `fallbackApprovers` slate included,
475+
the node fails with a retryable error starting `APPROVER_DIRECTORY_UNREADABLE:`
476+
that names the approver and the read, and writes no request. It is not
477+
opened on the rest of the slate, on the fallback or on the administrators,
478+
and it is not auto-approved. Run the flow again once the directory can be
479+
read. A decision on a request opened before approver snapshots existed still
480+
re-reads its slate the old way, which keeps the literal.
467481
- **A slate left empty, or holding only literals,** goes to the node's
468482
`onEmptyApprovers` policy, whose four values are listed under
469483
[Approving across organizations](#cross-org-approvers). Under the default,

0 commit comments

Comments
 (0)