Dry run expired
type | https://docs.frem.sh/reference/api/errors/dry-run-expired |
| HTTP status | 409 Conflict |
What it means
A legal change notice is sent with the id of a dry run, and that dry run is more than one hour old. Operator API only (POST /operator/legal-notices/{id}/send).
Example detail messages returned with this error:
- The dry run is 74 minutes old; a send needs one under 60. Run a new dry run and review it.
What to do
Run a new dry run (POST /operator/legal-notices/{id}/dry-runs), review its counts (recipients per tenant and language, and the tenants with no reachable admin), then send with the new dry_run_id.
The limit exists because a send mails exactly the recipient plan the dry run resolved. After an hour, owners and billing contacts may have changed, so the counts that were reviewed no longer describe what would be sent. A new dry run does not re-mail anyone: sending is idempotent, and an address the notice already reached for a tenant is skipped.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/dry-run-expired",
"title": "Conflict",
"status": 409,
"detail": "..."
}Branch on type, not on title or detail - those are human-readable and may be reworded.