Update recently? deleting

I expect these will delet by themselves overthe next hour or so one at a time. The issue is that until last week this activity worked flawlessly 60 or more times a days during testing. and now three systems are getting delayed on the archived and then delete function in the GUI.

Its completely repeatable.

all populations are identical (create board by owner public) (add other member)( add webhook integration) (add seven list elements)( add three card elements on first list item) (build three total boards).

Servers receiving webhooks are on the same VPC with that port open. API receiving is the web hook in a standard manner. Testing of webhook api endpoint works 100 times in a rows with POSTMAN with same payload that comes in from the webhook. All webhooks work correctly when they fire. Firing of webhooks happen when the refresh browser shows that board has finally deleted. There are no network errors anywhere that would explain the webhook not returning. There are no activites on the receiving api endpoint of the server getting the webhook until the wekan application decides to delete that board. I have no idea if the web hooks fires first and then deletes or deletes and then fires the webhook or of they are done in parallel. But they are time synched.

webhook syntax is :http><ipaddress:> <port>< api endpoint>

NO auth is included in the webhook

this is a ONE way web hook (not selected two way

you should be able to repeat this without any more details from me

LMK your thoughts or if my procedure is flawed

Thanks again

as expected the first of the three boards that was attempted to be deleted with the gui is now gone on browser refresh, the other two (in order) remain

that single webhook fired at the same time and worked without server errors and did what it was supposed to do on my end, it deleted several database rows in two different tables ( a card table for each card - 3 rows) and a list table that for each board has a row with all list ids for that board - 7 rows)

going to fix that NTP issue then try and figure out when the nightly check and update that is indicates is run between 2 and 4 AM shows a change in code

Would like to figure out when exactly that code was changed and then if possible what the version sub id is.

thanks

hint: although I deleted all three boards together initially, I thought they would delete one at a time. I was incorrect. after the first one actually get deleted you have to requeue each deletion. Meaning that the second and third deletes are not in queue, they are being thrown out till the one before it goes through. So after each delayed delete actually fires you have to go back and issue a new delete request for the next one

Hmm, I think I'll revert my in-progress Wekan background url feature code and make a new Wekan release with auth fixes

I mean Wekan background image feature code

it seems completely related to web hooks

Do you use LDAP ?

nope

I have two users (the admin who owns all api elements

and when I add boards another password based "user" is added to every board as a viewing member

are there any Rules at board?