> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # November 2026 > Documentation updates published in November 2026, grouped by required customer action. This page groups the updates by the action they require. Product filters show only the areas that affect your integration. See [News](https://docs.lerian.studio/en/news/news.md) for impact definitions. ## Action required *** **November 1, 2026** ### [Lerian SPB certificate activation and the two-operator close](https://docs.lerian.studio/en/rails/spb/spb-operations.md) The Lerian SPB pages and API reference moved to the newest Lerian SPB build. The rail reads the certifier code of an activation from the issuer of the certificate, so the activation request no longer carries `certifierCode`, and a body that sends it answers `422`. A certificate that you rotated before this release has no recorded certifier code, and its activation answers `SPB-0003`. Each statement day of a compulsory-deposit filing carries `mode`, `I` or `A`. Two operators can close as failed any message past its settlement deadline, not only a transfer, and can declare an LDL or LTR leg from an STR answer that the rail held unread. The rail now closes an LDL or LTR leg that it never sent when its STR grade closes or the day ends. Before you activate a certificate that you rotated before this release, rotate it again. Remove `certifierCode` from your activation requests. Send `mode` on each day of a compulsory-deposit filing. **November 1, 2026** ### [Lerian SPI Pix Automático answers and DICT query blocks](https://docs.lerian.studio/en/rails/spi/how-spi-works.md) The Pix Automático `pain.014`, `camt.029`, and `camt.055` requests of Lerian SPI take only the decision. The rail reads the participants and the identifiers from the message that it recorded, and any other field gets `422`. The DICT query block takes and returns `payerId`, the CPF or CNPJ of the end user, in place of `payerIdHash`. Upgrading removes every DICT query block. Send only the decision fields on these three requests. After you upgrade, place each DICT query block again with `payerId`. **November 1, 2026** ### [Lerian SILOC held requests and the LBTR cycle](https://docs.lerian.studio/en/rails/siloc/how-siloc-works.md) The Lerian SILOC pages and API reference moved to the newest Lerian SILOC build. Two different operators can now close an outbound request that is held for an answer Núclea never sent. `GET /api/v1/siloc/outbound/messages` takes `held=true` to list these requests. A `FAILED` request can therefore be one that Núclea may have received, and its `studio.lerian.br-siloc.siloc_outbound.failed` event carries the reason. An `LTR0002` or `LTR0008` for an operation whose earlier answer is live answers `409` and `SILOC-0026`. A `503` and `SILOC-0002` now means the command did not run. Do not treat a `FAILED` request as proof that it never reached Núclea. List the held requests. Have two operators close one only after you confirm with Núclea that it will not answer. Handle `SILOC-0026` in your integration. Send a request refused with `SILOC-0002` again with the same `X-Idempotency` key. **November 1, 2026** ### [Narya schedule spending ceiling and product sessions](https://docs.lerian.studio/en/platform/narya/automation-and-ci.md#schedules) The Narya pages moved to the newest Narya build. A schedule has a spending ceiling only when you set one, with `--budget` or `[schedules] ceiling_usd`. Narya no longer gives a new schedule a ceiling of `$5.00` per fire, and a stored schedule keeps the ceiling it has. A product session works on the API of a Lerian product, and its owner confirms each write. Workflow scripts can call tools with `callTool`, and Claude Code `Stop` hooks run when a turn ends. `config.toml` can declare endpoints that use plain `http`. A workflow run, or a session other than a product session, that you start over the API without `clientKind` is not attended, and Narya refuses its permission asks. Set a ceiling on each schedule that needs one. Run `narya schedule budget none` to remove a ceiling. Send `clientKind` `inline` or `tui`, or set the session posture to `attended`, when a person answers the asks. **November 1, 2026** ### [TED Lerian return errors and the daily close](https://docs.lerian.studio/en/reference/interfaces/ted-lerian/ted-lerian-error-list.md) The TED Lerian pages and API reference moved to the newest TED Lerian build. On the two incoming-return actions, `TED-1011` is an HTTP `422`. A return whose rail answer is unknown (`TED-1010`) stays requested until reconciliation or manual review closes it. When the ledger refuses a revert (`TED-1001`), the credit stays and the incoming transfer goes to manual review. At the daily close, a pending TED that the rail does not know moves to `AWAITING_RECONCILIATION`. Incoming return events carry `previousStatus`. Handle `TED-1011` as a `422` on the return actions. After a `TED-1010` on a return, read the status of the TED before you act again. Accept `AWAITING_RECONCILIATION` for a pending TED. ## Review recommended *** **November 1, 2026** ### [Access Manager v3.15.0: enroll a required MFA method during sign-in](https://docs.lerian.studio/en/platform/access-manager/features/mfa/api.md#enroll-a-required-method) In Access Manager v3.15.0, when the organization requires an MFA method that a user has not enrolled, sign-in answers `AUT-0019` with an MFA token that is valid only for enrollment. The user sets up and confirms the method with [Start MFA enrollment](https://docs.lerian.studio/en/reference/platform/access-manager/start-enrolling-a-required-mfa-factor.md) and [Confirm MFA enrollment](https://docs.lerian.studio/en/reference/platform/access-manager/confirm-an-mfa-enrollment-and-continue-the-login.md), and then completes the MFA challenge. Handle `AUT-0019` on Request Access Token and on Verify MFA Login. **November 1, 2026** ### [Console v3.0.0 optional operation routes and fee rounding](https://docs.lerian.studio/en/products/midaz/console/managing-accounting-routes#required-and-optional-operation-routes) The Console pages moved to Console v3.0.0. An accounting route can mark an operation route as optional, and a transaction may leave an optional route unused. The Console checks the route at **Go to Review** and again when you send. A fee package can round every fee it charges, with Midaz 4.4.0 or later. Most screens show dates and times in Brasília time, whatever the time zone of your browser. The Reporter screens group regulatory documents under **Regulatory Filings**: **Catalog**, **My Regulatory Documents** and **Filings**. Review your accounting routes, and mark as optional each operation route that some transactions leave unused. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.