-
Notifications
You must be signed in to change notification settings - Fork 17
Description
Under Resiliency on this page, there is a section that I believe needs to be reviewed because it mentions some types of failure, but only one of them is enumerated:
Golem automatically applies retry strategies to the following types of failures:
- HTTP Request Failures
In the case of errors which are not resolved on their own, Golem will eventually give up and mark the agent as failed. This is to prevent the system from getting stuck in an infinite loop of retries.
Under "Execution Semantics" section, we have:
In a future release, Golem will automatically generate idempotency keys for each request. For now, however, you can use the language-specific Golem SDK to generate an idempotency key, which you can then pass to the remote system.
Which I think also needs to be updated with regard to this PR.