Reporter error list

Error format Reporter returns errors as RFC 9457 problem details with the application/problem+json media type:

{
  "type": "https://errors.lerian.studio/v1/RPT-0012",
  "title": "Bad Request",
  "status": 400,
  "detail": "The specified templateID is not a valid UUID. Please check the value passed.",
  "code": "RPT-0012"
}

Field definitions

type – A URI that identifies the error in the Lerian error catalog. Built as https://errors.lerian.studio/v1/<code>.
title – The HTTP status text (for example, Bad Request).
status – The HTTP status code.
detail – Detailed guidance to help you resolve the error. For 5xx responses, Reporter always sanitizes the detail to internal error, so no internal cause leaks. Use code to branch programmatically.
code – A stable, unique identifier for the error (RPT-NNNN). Useful for programmatic handling and support requests.
errors – Optional list of per-field validation details, each with a message and a location.

Some messages contain placeholders such as %v or %s. Reporter replaces them with the specific values from your request.

Reporter errors

The tables below list the errors that can occur when you call the Reporter endpoints, what each one means, and how to resolve it.

400: Validation errors

`code`	Description	`detail`
RPT-0001	Missing required fields	One or more required fields are missing. Please ensure all required fields are included.
RPT-0002	Invalid file format	The uploaded file must be a .tpl file. Other formats are not supported.
RPT-0003	Invalid output format	The outputFormat field must be one of: html, csv, pdf, txt, or xml.
RPT-0004	Invalid header	One or more header values are missing or incorrectly formatted. Please verify required headers %v.
RPT-0005	Invalid File Uploaded	The file you submitted is invalid. Please check the uploaded file with error: %v
RPT-0006	Error File Empty	The file you submitted is empty. Please check the uploaded file.
RPT-0007	Error File Content Invalid	The file content is invalid because is not %s. Please check the uploaded file.
RPT-0008	Invalid Map Fields	The field on template file is invalid. Invalid field %s on %s.
RPT-0009	Invalid Path Parameter	Path parameters is in an incorrect format. Please check the following parameter %v and ensure they meet the required format before trying again.
RPT-0010	Update Output format without template File	Can not update output format without passing template file. Please check information passed and try again.
RPT-0012	Invalid templateID	The specified templateID is not a valid UUID. Please check the value passed.
RPT-0013	Invalid ledgerID	The specified ledgerID inside ledger ID list is not a valid UUID. Please check the value passed %v.
RPT-0014	Missing required fields	The fields mapped on template file are missing in the table schema or may be empty. Please check the fields passed: ‘%v’.
RPT-0015	Unexpected Fields in the Request	The request body contains more fields than expected. Please send only the allowed fields as per the documentation. The unexpected fields are listed in the fields object.
RPT-0016	Missing Fields in Request	Your request is missing one or more required fields. Please refer to the documentation to ensure all necessary fields are included in your request.
RPT-0017	Bad Request	The server could not understand the request due to malformed syntax. Please check the listed fields and try again.
RPT-0019	Invalid Query Parameter	One or more query parameters are in an incorrect format. Please check the following parameters ‘%v’ and ensure they meet the required format before trying again.
RPT-0023	Invalid Date Range Error	Both ‘initialDate’ and ‘finalDate’ fields are required and must be in the ‘yyyy-mm-dd’ format. Please provide valid dates and try again.
RPT-0024	Pagination Limit Exceeded	The pagination limit exceeds the maximum allowed of %v items per page. Please verify the limit and try again.
RPT-0025	Invalid Sort Order	The ‘sort_order’ field must be ‘asc’ or ‘desc’. Please provide a valid sort order and try again.
RPT-0026	Metadata Key Length Exceeded	The metadata key %v exceeds the maximum allowed length of %v characters. Please use a shorter key.
RPT-0027	Metadata Value Length Exceeded	The metadata value %v exceeds the maximum allowed length of %v characters. Please use a shorter value.
RPT-0028	Invalid Metadata Nesting	The metadata object cannot contain nested values. Please ensure that the value %v is not nested and try again.
RPT-0030	Missing Schema Table	The schema table %v is missing for data source ‘%v’. Please check the information passed.
RPT-0031	Missing Data Source Table	The data source %v is missing. Please check the value passed.
RPT-0032	Script Tag Detected	The template file contains a script tag and is not allowed. Please check the template file and try again.
RPT-0035	Ambiguous Schema Reference	The table ‘%v’ exists in multiple schemas: %v. Qualify it with its schema, as schema__%v.
RPT-0036	Schema Not Found	The schema ‘%v’ was not found in database ‘%v’. Please verify the schema name.
RPT-0037	Table Not Found in Schema	The table ‘%v’ was not found in schema ‘%v’ of database ‘%v’. Please verify the table name and schema.
RPT-0038	Database Not Registered	The database ‘%v’ is not registered. Please verify the datasource configuration.
RPT-0041	Bucket Required	The storage bucket name is required. Please check the storage configuration.
RPT-0042	Object Key Required	The object key is required for the storage operation.
RPT-0044	TTL Not Supported	TTL parameter is not supported in S3 mode. Use bucket lifecycle policies instead.
RPT-0046	Invalid Deadline Type	The ‘type’ field must be ‘regulatory’ or ‘custom’. Please provide a valid deadline type and try again.
RPT-0047	Invalid Deadline Frequency	The ‘frequency’ field must be one of: ‘once’, ‘daily’, ‘weekly’, ‘monthly’, ‘semiannual’, ‘annual’. Please provide a valid frequency and try again.
RPT-0048	Invalid Deadline Color	The ‘color’ field must be a valid hex color code (e.g., ‘#FF5733’). Please provide a valid color and try again.
RPT-0050	Months of Year Not Applicable	The ‘monthsOfYear’ field is not applicable for frequency ‘%v’. It can only be used with ‘semiannual’ or ‘annual’ frequencies.
RPT-0052	Months of Year Required	The ‘monthsOfYear’ field is required for frequency ‘%v’. Please specify which months of the year the deadline should recur on.
RPT-0054	Months of Year Out of Range	Each value in ‘monthsOfYear’ must be between 1 and 12. Received invalid value: %v.
RPT-0055	Due Date in the Past	The ‘dueDate’ must be today or a future date. Please provide a date that is not in the past.
RPT-0056	Months of Year Count Mismatch	The number of months in ‘monthsOfYear’ does not match the ‘%v’ frequency. ‘semiannual’ requires exactly 2 months and ‘annual’ requires exactly 1 month.
RPT-0059	Schema Validation Failed	The schema validation failed. Please verify the fields against the data source schema.
RPT-0062	Invalid UTF-8 Encoding	The ‘%v’ field contains invalid UTF-8 byte sequences. Please provide valid UTF-8 text and try again.
RPT-0073	Data Source Reserved Config Name	The `configName` is reserved for an operator-managed data source and cannot be assigned or renamed through the API.
RPT-0075	CRM Organization Scope Unresolved	The CRM data source organization scope could not be resolved, so the template cannot be safely saved.
RPT-0076	Filter Table Not Extracted	The filter table does not match any table mapped by the report template. Use one of the mapped tables.
RPT-0077	Filter Value Cannot Be Read As A Date	The filter value cannot be read as a date for the field. Use an ISO date or time value appropriate for that field.
RPT-0078	Template File Too Large	The template file exceeds the supported byte limit. Split the report into smaller templates and try again.
RPT-0079	Filter Operators Conflict	The filter combines operators that cannot be used together. Keep one compatible operator for the field.
RPT-0080	Data Source Field Invalid	A data source field is invalid. Correct the identified field and send the request again.
RPT-0090	Template Maps Too Many Columns	The template maps more columns than one report can process. Reduce the mapped columns or split the template.
RPT-0095	Filter Bound Has No Value	A filter operator has no comparable value. Provide a value or remove the operator.
RPT-0096	Filter Costs More Than A Query Can Carry	The filters exceed a query resource limit. Reduce the filter values or narrow the request.
RPT-0097	Filter Operator Carries The Wrong Number Of Values	The filter operator received the wrong number of values. For example, `between` requires exactly two values.
RPT-0105	Filter Value Cannot Be Read Against The Field It Filters	The filter value cannot be read as the type held by the field. Use a compatible value or a date-capable field.
RPT-0106	Invalid Cursor	The cursor was not issued by this API or no longer identifies a usable position. Restart the listing and follow `nextCursor`.
RPT-0107	Template Preview Failed	The template preview could not be rendered. Correct the template or sample data, then try again. The response detail identifies the specific refusal.
RPT-0110	Filter Period Cannot Share Its Field	The filter field uses `period` together with another operator. A period already states both ends of its range. Keep the period alone, or drop it and state both dates yourself.
RPT-0111	Reminder Filter Is Larger Than A Reminder Can Carry	The whole filter of the deadline exceeds what one deadline can store. Split it into more than one deadline, each naming fewer tables.
RPT-0112	Filter Names Something That Cannot Be A Name	A filter key cannot name a data source, a table, or a field. Correct the key. If an automation filled it, check the variable that feeds it.
RPT-0120	Template Category Is Required	The template has no category. Send `category` with the family the report is filed under, such as `cadoc`.
RPT-0121	Template Category Is Not A Usable Family Name	The category must match `^[a-z0-9_-]{1,100}$`. Reporter corrects case and surrounding spaces, but refuses an inner space, a dot, a slash, or an accent.
RPT-0122	Template Has No Category	The deadline names a template that has no category. File the template under a category, then send the deadline again unchanged.
RPT-0123	Too Many Templates In One Category Association	The request associates a category with more templates than one request can carry. Split the work into smaller batches.
RPT-0124	Category Association Names No Template	The request names no template. Send `templateIds` with at least one template ID.
RPT-0130	Invalid Deadline Timezone	The `timezone` field must be a valid IANA time zone name, such as `America/Sao_Paulo`.
RPT-0131	Filter Period Is Not A Known Window	The `period` value is not a window Reporter knows. Spell one of the windows the detail lists, exactly as written.
RPT-0134	Filter Condition Has No Operator	A filter field names no operator, so it would narrow the report by nothing. State an operator with its values, or remove the field from the filter.
RPT-0135	Data Source Uses A Reserved Name	The name `system` is reserved for the report’s generation parameters. Choose another `configName`.
RPT-0137	Invalid Document Contract	The regulatory document contract cannot be loaded. The detail names the point to correct.
RPT-0138	Value Rejected By The Document Contract	A value produced for a field is not allowed by the document contract. Correct the binding or the data behind it, then generate the report again.
RPT-0139	Regulatory Document Not In This Catalog	The template refers to a regulatory document this deployment does not carry. Name a document from the catalog.
RPT-0140	Missing Or Invalid Generation Parameter	A generation parameter the template declares is missing or invalid, or the template declares a parameter that is malformed. Correct the request’s `parameters` or the declaration.
RPT-0141	Template Marks A Position The Contract Does Not Declare	The template marks a field that the regulatory document contract does not declare. Correct the name in the template.
RPT-0142	A Regulatory Template Is Not Uploaded	A curated regulatory document takes its layout from the catalog, so no template file is uploaded for it. Supply the document and its data source, or create a custom report.
RPT-0143	Invalid Document Binding	The document binding cannot be read. The detail names the point to correct. Correct it and save the binding again.
RPT-0146	Invalid Subscription	The subscription cannot be used as it stands. The detail names what to correct.
RPT-0149	The Correction Cannot Be Applied	The correction is not valid for its position in the document. Correct it at the named position and apply it again.
RPT-0153	The Report’s Provenance Is Incomplete	The report’s frozen provenance record is missing a required element, so Reporter refused to record it. The detail names the element.
RPT-0154	The Catalog Content Is Not What Was Published	The catalog release failed its integrity check and was refused. The catalog in force is unchanged. Check the release and the path it came by.
RPT-0155	The Regulatory Release Cannot Be Fetched	The catalog origin could not supply the document’s files, so nothing was written. Try again when the origin answers. Documents already subscribed are unaffected.
RPT-0165	Template Has A Recursive Macro	A macro in the template calls itself, directly or through another macro, so rendering would never finish. Break the loop and upload the template again.
RPT-0166	Template Formats An Amount And Then Alters It	The template writes another filter after the `decimal` filter, which would put a wrong amount in the file. Move the other filter before `decimal`, or drop it.
RPT-0169	The Institution Is Invalid	A field of the institution is invalid: a blank name, a CNPJ whose check digits fail, or a malformed scope. Correct the field and send the institution again.
RPT-0173	No Midaz Organization Table	None of the named data sources holds the Midaz organization table, so there is no organization to propose an institution for. Name the data source of the Midaz onboarding database.
RPT-0174	The Data Source Is Not PostgreSQL	Reporter proposes institutions only from Midaz PostgreSQL databases. Leave the data source out, or name the data source of the Midaz onboarding database.
RPT-0175	More Than One Midaz Organization Table	The named data sources hold more than one Midaz organization table. Name only the data source of the Midaz onboarding database.
RPT-0180	Choose The Institution	The tenant has several institutions and the request names none. Set `institution` to one institution ID, or to `all` to read every institution’s rows in one report.
RPT-0181	The Institution Does Not Cover This Table	The report reads a table that the institution’s scope neither filters nor marks as shared. Add the table to the institution’s scope, then request the report again.
RPT-0183	The Institution Selection Is Invalid	The `institution` value is neither an institution ID nor `all`, or it is `all` on a regulatory filing, which declares exactly one institution.
RPT-0190	Choose The Institution That Files	A regulatory filing declares exactly one institution. The request names none, and the tenant does not have exactly one. Name the institution that files it, also on the subscription when the subscription predates institutions, and register one first if the tenant has none.

RPT-0075: CRM Organization Scope Unresolved

RPT-0075 is a fail-closed protection for templates that map plugin_crm. Reporter does not save or run an unscoped CRM mapping because that could expose records across Midaz organizations. It can occur while importing, creating, or updating a CRM template, and when a worker resolves an already-saved CRM template. Do not treat this code as proof that one environment variable is absent. It also occurs when Reporter cannot look up plugin_crm in the datasource registry. First confirm that the template maps plugin_crm, then check the Manager and worker configuration, registry availability, and the non-sensitive CRM connection settings. For a self-hosted deployment, configure the complete DATASOURCE_CRM_* block, including DATASOURCE_CRM_MIDAZ_ORGANIZATION_ID, and keep the CRM password and CRYPTO_HASH_SECRET_KEY_CRM / CRYPTO_ENCRYPT_SECRET_KEY_CRM in Secrets. Those crypto keys must be the same keys used by CRM, and DATASOURCE_CRED_ENC_KEY must remain stable. At Manager startup, the reserved datasource seed can fill an absent or empty metadata.midazOrganizationId. The seed never overwrites a non-empty persisted value. Do not create or PATCH plugin_crm through the ordinary datasource API. If a non-empty persisted organization ID is incorrect, stop the generic recovery and contact Lerian support. After an approved change, import or save the template, generate a report, confirm CRM fields decrypt, and verify organization isolation. See Reporter via Helm for the chart values.

401: Unauthorized

`code`	Description	`detail`
RPT-0158	Acting Subject Not Identified	The request was authorized but does not identify who is acting, and Reporter records each correction and approval against a person. Present a token that carries a subject claim. A deployment with authentication disabled cannot approve filings.

404: Not found

`code`	Description	`detail`
RPT-0011	Entity Not Found	No %v entity was found for the given ID. Please make sure to use the correct ID for the entity you are trying to manage.
RPT-0020	Invalid Date Format Error	The ‘initialDate’, ‘finalDate’, or both are in the incorrect format. Please use the ‘yyyy-mm-dd’ format and try again.
RPT-0021	Invalid Final Date Error	The ‘finalDate’ cannot be earlier than the ‘initialDate’. Please verify the dates and try again.
RPT-0022	Date Range Exceeds Limit Error	The range between ‘initialDate’ and ‘finalDate’ exceeds the permitted limit of %v months. Please adjust the dates and try again.
RPT-0043	Object Not Found	The requested object was not found in storage.
RPT-0057	Data Source Not Found	The requested data source was not found. Please verify the data source ID.
RPT-0147	Regulatory Document Unavailable	The regulatory document is not in this deployment’s catalog, or the deployment has no catalog. List the catalog to see which documents it carries.

409: Conflicts

`code`	Description	`detail`
RPT-0039	Duplicate Request In Flight	A duplicate request is currently being processed. Please wait and try again.
RPT-0040	Idempotency Conflict	A request with this idempotency key has already been processed.
RPT-0045	Duplicate Deadline	A deadline with the same name, type, due date, and frequency already exists. Please use different values or update the existing deadline.
RPT-0071	Data Source Config Name Conflict	A data source with the same `configName` already exists. Use a different `configName` and try again.
RPT-0072	Data Source In Use By Template	The data source is referenced by templates and cannot be deleted or renamed. Update or remove those templates first.
RPT-0144	The Binding Changed While You Were Editing	Someone saved the binding after you opened it. Reload the binding, apply your change on top, and save again.
RPT-0145	The Document Is Already Subscribed	The institution already files this document under another subscription. Edit that subscription’s binding, or cancel it first.
RPT-0150	The Draft Changed While You Were Editing	Someone corrected the draft after you opened it. Reload the draft, apply your correction on top, and try again.
RPT-0151	The Report Is Already Approved	An approved report does not change. To file something different, generate a new report.
RPT-0152	The Report Is Not A Draft	A correction applies only to a draft. The report is still generating, or its generation failed.
RPT-0156	Draft Has Required Fields Still Blank	Required fields in the draft carry no value. Fill each one with a correction, then approve or download the draft.
RPT-0167	Another Subscription Of The Document Is Active	Another subscription already files this document for the same institution. Deactivate that subscription first, or leave this one inactive.
RPT-0168	Data Source Built In	The platform provides this data source and it is read-only. You cannot update, delete, or test it, or register another data source under its name.
RPT-0170	The CNPJ Is Already Registered	The tenant already registered an institution with this CNPJ. Edit that institution, or delete it first.
RPT-0171	The Institution Changed While You Were Editing	Someone updated the institution after you read it. Read it again, apply your change on top, and save with the ETag it answers.
RPT-0182	The Institution Is In Use	Deadlines or active regulatory subscriptions still generate reports for this institution. Point the deadlines at another institution or delete them, deactivate the subscriptions, and delete the institution again.
RPT-0191	The Subscription Changed While You Were Editing	Someone changed the subscription after you read it. Read it again and write with the version it answers.

412: Precondition failed

`code`	Description	`detail`
RPT-0074	Data Source Credential Protection Not Configured	Credential protection is not configured. Set `DATASOURCE_CRED_ENC_KEY` and retry.

422: Unprocessable

`code`	Description	`detail`
RPT-0029	Report status not Finished	The Report is not ready to download. Report is processing yet.
RPT-0157	Stored Artifact Does Not Match Its Provenance	The stored file’s checksum does not match the checksum frozen when the report was rendered, so Reporter does not hand the file out. Regenerate the report, or investigate the storage.

428: Precondition required

`code`	Description	`detail`
RPT-0148	The Binding Version Is Required	Saving a binding requires the `If-Match` header with the ETag from the last read. Read the binding again and save with that ETag.
RPT-0172	The Institution Version Is Required	Updating an institution requires the `If-Match` header with the ETag from the last read. Read the institution again and save with that ETag.
RPT-0192	The Subscription Version Is Required	Changing a subscription requires the `If-Match` header with the version from the last read. Read the subscription again and write with that version.

429: Too many requests

`code`	Description	`detail`
RPT-0108	Template Preview Busy	All configured concurrent template preview slots are in use. The template was not rejected; try the preview again shortly.

500: Server errors

`code`	Description	`detail`
RPT-0018	Internal Server Error	internal error
RPT-0034	Communication Error with SeaweedFS	internal error

Every unexpected failure during synchronous endpoint handling surfaces as HTTP 500. The response carries code: RPT-0018, or code: RPT-0034 when the file storage fails, and a sanitized internal error detail. Internal causes never leak into the response body. Asynchronous worker and report-generation failures instead follow the report statuses and metadata described below. Reporter does not return them to the original request as HTTP 500.

Report-generation errors (asynchronous)

Report generation runs asynchronously in the worker. The original HTTP request never receives a failed data-extraction section. The report ends with status Error when all sections fail, or Partial when some fail. In either case, metadata.error_code is RPT-0060. The keys of metadata.sections are database names. Each failed entry contains its classified error_code (RPT-0018 for an untyped failure). An RPT-0075 entry also carries a remediation message. Other worker failures end with status Error and a safe non-RPT metadata.error_code of report_generation_failed, report_generation_timeout, report_generation_canceled, or report_message_schema_unsupported. These failures have no sections map and do not retain the underlying RPT code. A report whose worker stopped reporting that it was alive ends with status Error and metadata.error_code RPT-0160.

`code`	Description	Meaning
RPT-0058	Data Source Unavailable	The data source is currently unavailable. Results may be incomplete.
RPT-0060	Extraction Job Failed	The extraction job failed. Please try again later or contact support.
RPT-0061	Template Rendering Failed	The template could not be rendered with the provided data. This is a permanent error and will not succeed on retry.
RPT-0063	CRM Hash Key Not Configured	CRM hash key not configured.
RPT-0064	CRM Encrypt Key Not Configured	CRM encrypt key not configured.
RPT-0065	Record Decryption Failed	Record decryption failed.
RPT-0066	Cipher Init Failed	Cipher initialization failed.
RPT-0067	Invalid Extracted Data	The extracted data is invalid.
RPT-0068	Unexpected Collection Result	The data collection returned an unexpected result.
RPT-0069	Data Source Not Found	The data source referenced by the report was not found.
RPT-0070	Data Source Unavailable	The data source was unavailable during extraction.
RPT-0136	Unsupported Report Message Schema Version	The worker received a report message written for a newer schema version than it supports, and refused it. The report ends with status `Error` and `metadata.error_code` `report_message_schema_unsupported`. Generate the report again once every worker runs the newer build.
RPT-0160	Report Worker Lost	The worker that owned the report stopped reporting that it was alive, so Reporter ended the report with status `Error`. Look for a stopped or frozen worker.
RPT-0161	Row Ceiling Exceeded	A data section matched more rows than the data source’s configured row ceiling. The section fails instead of returning a truncated result. Narrow the report filter or raise the data source’s row ceiling.
RPT-0162	Data Source Query Timeout	A data section’s query did not finish within the data source’s configured query timeout. Narrow the report filter or raise the data source’s query timeout.

Scheduled generation errors (logged)

The deadline scheduler raises these codes. It runs in the Manager when DEADLINE_TRIGGER_ENABLED=true. It answers no request, so the codes appear only in its log lines, never in an HTTP response. Each code is in the error_code field of its log line, except RPT-0113, which appears only in the error field. When a refusal cannot clear by retrying, a second line reports it with error_code RPT-0118 and carries the original code in error.

`code`	Description	Meaning
RPT-0113	Reminder Names No Template To Read A Family From	The deadline came due but names no template, so there is no report family to generate. The occurrence is still announced. If the deadline should produce a report, give it a `templateId` whose template has a category.
RPT-0114	Template Has No Family At Dispatch	The deadline’s template has no category when the scheduler dispatches it, so no report is generated. File the template under a category.
RPT-0115	Scheduled Generation Could Not Verify Its Tenant	The scheduler could not confirm the tenant that owns the deadline, so it wrote nothing.
RPT-0116	Reminder Window Could Not Be Resolved At Dispatch	The scheduler could not resolve the data window of the occurrence, so no report is generated for it. Save the deadline again with a window Reporter knows.
RPT-0117	Scheduled Report Generation Was Refused	Report generation refused the scheduled request. The log line carries the underlying refusal.
RPT-0118	Scheduled Generation Not Retryable	Qualifies a refusal that repeats on every occurrence until someone changes the deadline, the template, or the filter.
RPT-0119	Scheduled Generation Exhausted	The same refusal repeated on consecutive occurrences, so the scheduler stopped attempting generation for this deadline. The announcement still goes out.
RPT-0132	Scheduled Occurrences Skipped	Occurrences came due and were stepped over when the scheduler advanced. Each skipped occurrence produced no report. This is a notice, not a failure.
RPT-0133	Scheduled Catch-Up Incomplete	The scheduler produced part of a deadline’s backlog, and the next run continues from where it stopped. `catch_up_stop_reason` is `tenant_budget_spent` (a warning) or `ceiling_reached` (an error: investigate the delay).

Getting started

Templates API

Template Builder API

Reports API

Deadlines API

Data Sources API

Institutions API

Regulatory Catalog API

Regulatory Subscriptions API

Regulatory Bindings API

Regulatory Reports API

Metrics API

Streaming API

Error handling

Events

Reporter error list

Reporter errors

400: Validation errors

RPT-0075: CRM Organization Scope Unresolved

401: Unauthorized

404: Not found

409: Conflicts

412: Precondition failed

422: Unprocessable

428: Precondition required

429: Too many requests

500: Server errors

Report-generation errors (asynchronous)

Scheduled generation errors (logged)

​Reporter errors

​400: Validation errors

​RPT-0075: CRM Organization Scope Unresolved

​401: Unauthorized

​404: Not found

​409: Conflicts

​412: Precondition failed

​422: Unprocessable

​428: Precondition required

​429: Too many requests

​500: Server errors

​Report-generation errors (asynchronous)

​Scheduled generation errors (logged)

Reporter errors

400: Validation errors

RPT-0075: CRM Organization Scope Unresolved

401: Unauthorized

404: Not found

409: Conflicts

412: Precondition failed

422: Unprocessable

428: Precondition required

429: Too many requests

500: Server errors

Report-generation errors (asynchronous)

Scheduled generation errors (logged)