You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A 200 is received and the document is consistently removed from S3, but is not always removed from DynamoDB in a short amount of time (< 3 seconds). The metadata is retrieved on subsequent searches for a few seconds at least, but when a delete is attempted again, a 404 is provided, but the item is no longer available in search.
The text was updated successfully, but these errors were encountered:
reganwolfrom
changed the title
DELETE does not consistently remove file from DynamoDB (possibly related to document control/versions)
DELETE has a delay in removing file from DynamoDB
Mar 10, 2023
New Feature
#182 - Document Retry - documents that fail to process are added to a queue for reprocessing
#192 - Added POST /documents/{documentId}/actions/retry for retrying of failed document actions
#196 - Added OCR support for PDF Portfolio files
#194 - Added support for document content to be a "deep link"
#189 - Added document "soft delete"
#146 - Added insertedDate, completedDate to Document actions
#171 - Added Document Workflows
#179 - Added Cognito group that allows authentication but no authorization
#170 - Added Notification action
#168 - Added SMTP support to /configuration API
#169 - Added /groups API
#201 - Added version of FormKiQ that can be run via Docker
Updates
#166 - AWS Lambda end of support for Custom Runtime based on Amazon Linux 1
#188 - Intelligent document processing with OpenAI, uses Schemas to improve results
#119 - improved performance when removing documents
Bugs Fixes#172 - Fixed Fulltext action ending up in a bad state
#185 - Fixed GET /documents/{documentId}/url returns full path of document instead of filename
#197 - POST /documents/compress is not available for users with READ ONLY access
When running a delete endpoint:
curl 'https://{host}/documents/69648100-6efd-4764-8f80-e9a886a7dc1d?siteId={siteId}'
-X 'DELETE'
-H 'authority: {authority}'
-H 'accept: /'
-H 'accept-language: en-CA,en-GB;q=0.9,en-US;q=0.8,en;q=0.7,fr;q=0.6'
-H 'authorization: {authorization}'
-H 'origin: http://localhost:4200'
-H 'referer: http://localhost:4200/'
-H 'sec-ch-ua: "Chromium";v="110", "Not A(Brand";v="24", "Google Chrome";v="110"'
-H 'sec-ch-ua-mobile: ?0'
-H 'sec-ch-ua-platform: "macOS"'
-H 'sec-fetch-dest: empty'
-H 'sec-fetch-mode: cors'
-H 'sec-fetch-site: cross-site'
-H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36'
--compressed
A 200 is received and the document is consistently removed from S3, but is not always removed from DynamoDB in a short amount of time (< 3 seconds). The metadata is retrieved on subsequent searches for a few seconds at least, but when a delete is attempted again, a 404 is provided, but the item is no longer available in search.
The text was updated successfully, but these errors were encountered: