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
Hi.
I'm having event rules für provider add and update.
On both events are actions, that connects to an other backend to do some special things.
If event provider add occurs, my backend stops the event rule for provider update, take some actions and do a http:put to a user.
As soon as I start the event rule for provider update, sftpgo goes into a loop of death:
provider event update triggered -> my backend triggers -> provider event update triggered and so on.
Do sftpgo save all events, even if the corrosponding rule is not active and starts to work on all events that comes after disabling then event rule?
How to prevent this?
Thx in advance
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
-
Hi.
I'm having event rules für provider add and update.
On both events are actions, that connects to an other backend to do some special things.
If event provider add occurs, my backend stops the event rule for provider update, take some actions and do a http:put to a user.
As soon as I start the event rule for provider update, sftpgo goes into a loop of death:
provider event update triggered -> my backend triggers -> provider event update triggered and so on.
Do sftpgo save all events, even if the corrosponding rule is not active and starts to work on all events that comes after disabling then event rule?
How to prevent this?
Thx in advance
Beta Was this translation helpful? Give feedback.
All reactions