Actions26
- Основные Отчёты Actions
- Отчёт Об Остатках На Складах Actions
- Отчёт О Товарах C Обязательной Маркировкой Actions
- Отчёты Об Удержаниях Actions
- Платная Приёмка Actions
- Платное Хранение Actions
- Продажи По Регионам Actions
- Доля Бренда В Продажах Actions
- Скрытые Товары Actions
- Отчёт О Возвратах И Перемещении Товаров Actions
- Динамика Оборачиваемости Actions
Overview
This node interacts with a specific API to retrieve reports related to retention analytics, specifically focusing on "Incorrect Attachments" within a given date range. It is useful for users who need to analyze and audit attachment errors or inconsistencies in retention reports over a specified period. For example, a user might want to fetch all incorrect attachment records from February 28, 2025, to March 21, 2025, to identify patterns or issues in document handling.
Properties
| Name | Meaning |
|---|---|
| Date From | The start date of the reporting period in YYYY-MM-DD format. Defines the beginning of the data range to query. |
| Date To | The end date of the reporting period in YYYY-MM-DD format. Defines the end of the data range to query. |
Output
The node outputs JSON data containing the analytics report about incorrect attachments within the specified date range. The exact structure depends on the API response but typically includes details such as attachment identifiers, error types, timestamps, and possibly metadata related to the retention reports. There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential for authentication with the external service providing the retention reports.
- The node uses a base URL defined in an imported Swagger/OpenAPI specification.
- The node expects the environment to have access to this API endpoint and proper network connectivity.
Troubleshooting
- Common Issues:
- Invalid date formats may cause the API request to fail. Ensure dates are in
YYYY-MM-DDformat. - Missing or invalid API credentials will result in authentication errors.
- Network connectivity problems can prevent successful API calls.
- Invalid date formats may cause the API request to fail. Ensure dates are in
- Error Messages:
- Authentication failures usually indicate missing or incorrect API keys; verify and update credentials.
- Validation errors on date parameters suggest incorrect formatting or logical errors (e.g.,
dateFromafterdateTo). - Timeout or connection errors imply network issues or API unavailability; retry later or check network settings.
Links and References
- No direct links provided in the source code.
- Users should refer to the external API documentation for detailed information on the retention reports and the "Incorrect Attachments" analytics endpoint.