SIGNALS Documentation
API Reference

Limitations

Known limitations of the current release, gathered from across the documentation, with a link to the page that explains each one.

Last reviewed against source:

Signals is pre-1.0 and in beta. This page collects limitations that the documentation already states in detail elsewhere, so you can check them before you plan around a feature. Each entry links to the page that covers it.

Pricing and catalogue

Limitation Detail
Surcharge criteria are not on the admin form Criteria such as catalogue item groups, tags and valid dates exist in the backend but the surcharge group form does not show them. See Pricing.
Surcharge groups cannot be toggled on a rental from the web interface toggle_surcharge_group is available through the API only. See Pricing.
A discount category cannot be applied by hand from the web interface Manual application is API-only. Discounts reach a rental through the account's discount category and the auto-apply rules. See Pricing.
No Add to rental action on a catalogue item Open or create the rental and add the item there. See Catalogue items.

Documents and numbering

Limitation Detail
reset_frequency is API-only The setting that restarts a document counter each year or month is set with PUT /api/v1/document_sequences/{id} and is not shown in the sequence edit modal. See Numbering.

Accounts and privacy

Limitation Detail
accounts.merge.accept_new cannot be edited The key is not registered in the account settings, so neither the settings screen nor the settings API can change it. To stop new merges, withdraw the accounts.merge permission from the roles that hold it. See Accounts.
Complete erasure is not guaranteed across every store Derived, external and backup copies of erased data are not covered. See Accounts and Backup and Restore.

Invoicing, payments and billing runs

Limitation Detail
Refunds cannot be recorded from the invoice page The invoice page has no refund form. Refunds are recorded through REST or MCP and must name their original payment. See Invoicing & Payments and Recording a Payment.
Provider-initiated refunds, chargebacks, unapplied manual cash and bank reconciliation are not available Invoices, credits and payments recorded before postings were introduced are not given guessed postings. See Invoicing & Payments.
Refunding pure unapplied cash is not available The receipt stays investigable and shows Refund unavailable. See Payments.
Allocation reversal and chargebacks are staff commands only Neither is available through the API or the interface. See Payments.
Write-offs are dated the current UTC day See Invoicing & Payments.
Retry failed item on a billing run is not available Do not reset a failed item to Ready or reissue a posted invoice. See Billing runs.
The unresolved tax zone fallback is seller_domestic only See Finance settings.
The base currency cannot be changed once financial records exist A new base is allowed only for an installation with no document families or financial postings. See Multi-currency.
Currencies are read-only over the API They are reference data. See Multi-currency.

Features that are off by default

Feature How to turn it on
Imports Set SIGNALS_IMPORTS_ENABLED=true in .env. While off, the import API, admin pages and earlier URLs are unavailable. See Imports.
Magic-link login An admin or owner enables it in Settings → Security → Magic-Link Login. See Authentication & Settings.
API throughput enforcement Set API_METERING_THROUGHPUT_ENFORCE=true. See API authentication.

Platform

Limitation Detail
API compatibility guarantees are not yet in force Signals has not shipped 1.0, so genuine defects in the wire contract may be corrected even where that would later count as a breaking change. See API versioning.
Put-aside holds are not created The put-aside demand source is not built, so nothing creates a put-aside hold and the scheduled release task does nothing. See Scheduled Tasks.
No built-in scheduled backups Signals only dumps the database before signals:update. Take regular backups with your own tooling. See Backup and Restore.
Reference Use it for
Glossary Terms used in the interface
Upgrading Breaking changes in this release