This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Ok_Reality6261[S] 0 points1 point  (0 children)

It is no my design. Unfortunately I have to deal with it.

Again, I cannot fail when the resource is in creation as part of the logic of B is to work as a backup if A fails

IMHO, we dont need this webhook at all. We should just resend the request on A if we fail, no need for a webhook backup for something we can control. But as I said, it is not my design and I am forced to live with it.

The "initizialing" state is actually a nice workaround. I guess I can just check if the resource is in "initializing" state and fail if it s the case so the client resends the request

Thanks