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
When Foliage issues a Folio command to delete a record, and the response times out, Folio may have completed the action, but Foliage thinks it failed (because of the timeout), so it retries it after a delay. Then, when Foliage retries the deletion command, it gets a 404 from Folio (because the record no longer exists) and thinks that that is a problem.
What Foliage should do instead is to take note of the fact that it is retrying a command due to a timeout, and if it gets a 404 in the retry, assume that the 404 means the first command actually went through instead of having failed.
This will require changes to delete_tab.py.
The text was updated successfully, but these errors were encountered:
When Foliage issues a Folio command to delete a record, and the response times out, Folio may have completed the action, but Foliage thinks it failed (because of the timeout), so it retries it after a delay. Then, when Foliage retries the deletion command, it gets a 404 from Folio (because the record no longer exists) and thinks that that is a problem.
What Foliage should do instead is to take note of the fact that it is retrying a command due to a timeout, and if it gets a 404 in the retry, assume that the 404 means the first command actually went through instead of having failed.
This will require changes to
delete_tab.py
.The text was updated successfully, but these errors were encountered: