📚 Documentation: Updating Document via Cloud Function runs with Event [document.update] in loop

[anandsubbu007]

💭 Description

when i try to alter the data which is created or updated via event trigger.
it runs in loop.

how to prevent it from running in loop

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[Meldiron]

I can imagine there are multiple ways to prevent it. What I have seen people doing in the community is to have updatedAt attribute on the document, and update it each time a function updates the document.

To prevent the loop, in the function you can check how big a difference between updatedAt and the current time is. If it is something smaller than 1 second, it means the loop is starting, and in such a case, simply stop the execution. This way 2 executions are created, but the second is stopped as soon as it realises it's creating a loop.

[anandsubbu007]

is there way to stop function if it runs in loop?

[Meldiron]

To stop a function, make sure you don't update the document again. The best solution would be to do the check right at the top of your function - if the difference between updatedAt in the function and Date.now() is too small, return the response immediately return $response->send('Stopped to prevent infinite loop.').

[OHeroJ]

createdAt updatedAt is something that should have been available with appwrite. Otherwise, the best example is provided, instead of users constantly trying to make mistakes。

After 2 days of experience, I feel sorry for the 22k github stars, and from the user's point of view, the development is inefficient and frustrating.

[stnguyen90]

createdAt updatedAt is something that should have been available with appwrite

@OHeroJ, thanks for your feedback. 🙏 These attributes should be available by default as of 0.15.0!

@anandsubbu007, do you have any other questions or can this issue be closed?

[stnguyen90]

Closing due to inactivity and since we have $createdAt and $updatedAt now.