Update trigger projects, triggers update of all time tracking records related to the relevant project

[PurleGorilla]

What is your question?

We use the trigger in time tracking and projects in awork, in order to send data to a web hook. Last week some tags in projects got updated. This should trigger 'update project'. But on top of that it triggered 'update time tracking' for all records which are related to this project. This resulted in 5000 update trigger, which caused a big mess on our side. In my opinion its not logic to update time tracking records when projects are altered. what's the reason behind zthis odd behavior and how can it be prevented?

Do you have a trace id of the call?

No response

[sebastianrosch]

Hi @PurleGorilla, thank you for reporting this.
In many cases, the project including their tags are nested models in other entities and therefore need to be updated as well. I understand that this can cause a lot of webhook requests. We'll look at a way to make this more transparent and configurable.

What would you expect here?

[PurleGorilla]

The problem is that tags are not really related to time tracking. Is this behavior really necessary? If yes, can you send some information why it was triggered. If I knew I could filter this cases out on my side. Otherwise I don't have a chance to know whether it's a real updated time tracking record or 'fake' triggered by the changes of tags.

[PurleGorilla]

Would you be available for a short call?

[PurleGorilla]

Is it possible to send a different eventType, such as 'tagupdated'. By this I would know the difference.

[sebastianrosch]

Hi @PurleGorilla, sorry I was off at the end of last week. This week I only have a time slot at 3:30pm CET tomorrow, or 10am CET on Wednesday.

The behavior is necessary as it is how our models are structured and our architecture is set up. We use the same event handling infrastructure internally, for our web app, as we use for webhooks. We need to be able to pass information also on nested properties as our data uses this. Unfortunately, in this case it creates a lot of different events for consistency reasons.

I just checked and we are not sending the actual changes via the webhook event, so at the moment it is not possible to identify what exactly has changed. We are considering adding this to the webhooks.

[PurleGorilla]

Hi, Thanks for the reply. That also means, that all your customer using your API face the same issue? Are we the first one, having issues with that? My customer really needs a solution for that. Maybe you got an idea how to handle that. Any best practice? Sorry for my late response. I just became father and had some baby issues to handle :) How about a short call today or tomorrow? You can just call me. Looking forward talking to you asap. Mit freundlichen Grüßen Dipl. Wi-Ing. Emanuel Neubert

…

Am 12.02.2024 um 20:16 schrieb Sebastian ***@***.***>: Hi @PurleGorilla <https://github.com/PurleGorilla>, sorry I was off at the end of last week. This week I only have a time slot at 3:30pm CET tomorrow, or 10am CET on Wednesday. The behavior is necessary as it is how our models are structured and our architecture is set up. We use the same event handling infrastructure internally, for our web app, as we use for webhooks. We need to be able to pass information also on nested properties as our data uses this. Unfortunately, in this case it creates a lot of different events for consistency reasons. I just checked and we are not sending the actual changes via the webhook event, so at the moment it is not possible to identify what exactly has changed. We are considering adding this to the webhooks. — Reply to this email directly, view it on GitHub <#166 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AS5SKPGPADNDNEBZFUYJ7WTYTJTCBAVCNFSM6AAAAABC2ZKJC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZZGM3TMNJYGA>. You are receiving this because you were mentioned.

[sebastianrosch]

Hi @PurleGorilla, first of all: congrats! All the best to the new family!

In theory, yes. However, I have not heard of anyone reporting issues with this. Renaming a tag is not a common use case, so maybe nobody has run into this issue yet.

What is the issue the additional events are causing on your end?

I am currently not in Germany and don't have good phone service here. I could offer a Zoom call at 3pm or 4pm today if that works. I will reach out via email.

[sebastianrosch]

Actually it seems like I can't see your email and your domain does not seem to exist. Can you send me a message at [email protected]? Thanks

[PurleGorilla]

Hi, Thanks for the Congrats and the fast reply. 4pm would be good. I’m sending an invitation by calendar.

[sebastianrosch]

Hi @PurleGorilla, thanks I received the link. Speak later!

Please be aware that responding here posts the entire email publicly on Github. I have removed sensitive information from your message.

[PurleGorilla]

Thanks :)