> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-10-16 — Forge updates

> Knowledge source modes are now synchronize and live everywhere; sync and federated are refused. Knowledge sources that deliver records write each page in one step and embed searchable records afterwards, in batches. The synthesis queue, held procedure drafts, judge panel admissions and curator recommendations are group human tasks, listed in My Work to everyone holding the queue's permission.

**2026-10-16**

Knowledge source mode names.

A knowledge source's `mode` is now `synchronize` or `live` on every surface: the
[create a source](https://docs.gloo.com/forge/reference/http-api/knowledge/create-source.md) route, the source and health
reads, the MCP knowledge source tools and the Console. The earlier names `sync` and `federated`
are refused on input and are no longer returned. See
[External knowledge sources](https://docs.gloo.com/forge/knowledge/external-sources.md).

**2026-10-16**

Record sources sync a page at a time.

A knowledge source that delivers typed records, such as Freshservice, now writes each listed page
of records in one step instead of one record at a time. Records of a searchable kind are embedded
for search shortly afterwards, in batches; records of a kind that is not searchable are no longer
embedded. Freshservice is listed 100 items a page. A record is not returned by search until its
batch is embedded; `list` and `get` return it at once.

During a source's first pass, its drawer in the Console shows the collection the pass is on, how
many records it has stored and how long it has run, and lets you browse the records stored so far,
labelled as not yet complete. See
[External knowledge sources](https://docs.gloo.com/forge/knowledge/external-sources.md).

**2026-10-16**

Human tasks, Increment 3b-1: the review queues are group human tasks.

## Changed

* The synthesis queue (requests awaiting review and provisional requests), held procedure drafts, judge panel admissions and curator recommendations are now group human tasks. An item asks everyone who holds the queue's permission at the platform scope now and is an active person with an email: `synthesis:approve` for the synthesis queue, judge admissions and curator recommendations, and `approvals:approve` for held procedure drafts. Someone granted the permission later is asked at once. See [Review queues](https://docs.gloo.com/forge/reference/http-api/governance#review-queues).
* Deciding an item from its queue page, from [My Work](https://docs.gloo.com/forge/console/my-work.md#review-queues), with a Personal key through the [human task routes](https://docs.gloo.com/forge/reference/http-api/governance#deciding-through-the-api), or through the queue routes of `/api/v2/synthesis` and `/api/v2/judges` goes through the item's task. A Personal key decides as its owner: `promoteRequests`, `demoteRequests`, `acceptRequests` and `closeKeepBothCuratorRecommendations` skip an item that does not ask the owner as `not_a_candidate` and one someone else claimed as `claimed_by_other`; `judges/resolveAdmission` and `synthesis/decideCuratorRecommendation` answer `403` and `409` for the same cases. A platform key or an External App decides as before and closes the item's open task.
* The queue pages and My Work show who has claimed an item, with **Claim** and **Release**. **Not me**, with a reason, stops Forge reminding you about one item; you stay able to decide it. **Take over** moves someone else's claim to you and needs `approvals:approve` at the platform scope. `listMyWork` and `forge_list_my_work` list review-queue items as `kind: "human_task"`, at most 50 per queue; when a queue holds more, the last one listed carries `queueOverflow: true`. `reassignHumanTask` and `forge_reassign_human_task` accept `kind: "human_task"` with the owner alone as the assignee, which takes over the claim.
* A review-queue item sends nothing when it opens. A daily digest at 13:00 UTC (event `human_task.digest`) sends each person one bell notification and one email per queue for items that have waited 7 days or more, following their notification preferences. Items past their 14-day due date are also reported to administrators (holders of `approvals:approve` at the platform scope). An item stays open until someone decides it; it is never canceled for lateness.
* Review-queue items are not listed on Slack's Home tab, in `/forge approvals` or in **Waiting on me**. A person whose digest frequency is off sees them only in My Work.
* The Synthesis Queue and Admissions pages open with `platform:read`, and their decision controls appear only with `synthesis:approve`. The Curator Queue page needs `synthesis:approve`. None of the three asks for the platform administrator role any more.

## Added

* **Reject at review.** The synthesis queue can reject a request awaiting review: **Reject** on the Console page, or `demoteRequests` / `forge_demote_synthesis_requests` on an `awaiting_review` request. The request becomes `rejected` with the fixed failure reason `operator_rejected_at_review`, and the rejection is recorded so the same specification is not synthesized again. See [Demote synthesis requests](https://docs.gloo.com/forge/reference/http-api/synthesis/demoteRequests.md).

## Removed

* The synthesis watchdog's overdue Slack channel alerts no longer fire, and neither do the admin webhooks `synthesis.review_overdue` and `synthesis.promotion_overdue`. The two event names stay in the catalog. The daily digest replaces them.

## Migration

* The backfill `human-task-queues-v1` issues a task for every item open at deploy, without notifying anyone. Those tasks follow up 7 days after the deploy and are due 14 days after it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.