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
I'm using the webhook as a sort of post-save decoration service, which means i catch saves of entries, send the webhook, do some external data preparation and then updating the entry via graphQL. I realize this might not be the most common way of doing things, but the problem I run into is that it will be causing an infinite update loop because graphQL updates of entries trigger the same webhook.
I seem to neither be able to identify changed fields of the entry, or the actual source of the change, hence, no way of filtering out hooks that are trigger via GraphQL. Would there be such a possibility?
I was hoping that the duplicateOf property was actually the previous revision of the entry, but that doesn't seem to be the case. I am somewhat confused regarding the duplicateOf entity and the IDs that are passed with the payload. The sender object always have a different ID than the duplicateOf object, but it seems to be the duplicateOf that has the "correct" ID of the entry...?
This discussion was converted from issue #40 on August 30, 2021 21:04.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Description
I'm using the webhook as a sort of post-save decoration service, which means i catch saves of entries, send the webhook, do some external data preparation and then updating the entry via graphQL. I realize this might not be the most common way of doing things, but the problem I run into is that it will be causing an infinite update loop because graphQL updates of entries trigger the same webhook.
I seem to neither be able to identify changed fields of the entry, or the actual source of the change, hence, no way of filtering out hooks that are trigger via GraphQL. Would there be such a possibility?
I was hoping that the
duplicateOf
property was actually the previous revision of the entry, but that doesn't seem to be the case. I am somewhat confused regarding the duplicateOf entity and the IDs that are passed with the payload. The sender object always have a different ID than theduplicateOf
object, but it seems to be theduplicateOf
that has the "correct" ID of the entry...?Beta Was this translation helpful? Give feedback.
All reactions