Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Endpoint to retry failed document actions #192

Closed
mfriesen opened this issue Nov 18, 2023 · 1 comment
Closed

Add Endpoint to retry failed document actions #192

mfriesen opened this issue Nov 18, 2023 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@mfriesen
Copy link
Member

With GET /documents?actionStatus=FAILED now returning failed document actions status. It would be nice to add an ability to retry this failed action.

Maybe an point like
PATCH /documents/{documentId}/actions/{FAILED} would be nice.

possible
PATCH /documents/actions/{FAILED} to loop through all failed actions and retry them all. Would be nice if there was a mass failure for some reason.

@mfriesen mfriesen added the enhancement New feature or request label Nov 18, 2023
@mfriesen mfriesen added this to the v1.13.0 milestone Nov 18, 2023
@reganwolfrom
Copy link
Member

@mfriesen While a PATCH for all could work, I feel like in most cases, the goal will be to retry some documents' actions, not all. Plus, if a document action fails, isn't that FAILED action still listed, even after the document action is retried? For audit purposes we would not want to remove that failure, but submit a new set of one or more actions for retry. So the PATCH would then continually retry for any action that ever failed, even if retried.

To be honest, I think the best way to handle this for now, while we do not have IDs for individual action requests, is to not include a retry endpoint, but to allow the user to script retries based on the results of the actionStatus=FAILED GET.

If we eventually add IDs to individual action requests, we could then have a POST /documents/{documentId}/actions/{actionId}/retry

(I'm thinking "retry" vs. "retries", simply because you should not have more than one "retry" at a time for an action.)

@mfriesen mfriesen closed this as completed Dec 1, 2023
mfriesen added a commit that referenced this issue Jan 22, 2024
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants