
I'm currently using Appwrite's functions.createExecution
in my project. I want to avoid double requests when multiple actions (like searching or pagination) are triggered in quick succession.
When using fetch, I usually rely on AbortController with a signal to handle this. However, I'm unsure how to implement a similar approach with functions.createExecution
.
Here's an example of the code I’m using:
TypeScript
const result = await functions.createExecution(
"name_function",
undefined,
false,
`/path-to-function`,
ExecutionMethod.GET
);
TL;DR
Issue: Developer using Appwrite's `functions.createExecution` wants to prevent double requests when multiple actions occur in quick succession like searching or pagination.
Solution: To avoid double requests, developers can create a mechanism to track and prevent concurrent executions. One possible approach is to set a flag or use a queue system to manage the execution flow and prevent multiple calls to `functions.createExecution`. This can help ensure that only one request is processed at a time, avoiding duplication of actions.Recommended threads
- My collection is not updating after csv ...
- phantom relationships appear on parent c...
i have this bug were my past deleted collection apears as relationship to my parent collection. when i try to delete that relationship from parent it gives me e...
- Attribute stuck on proccessing
i tried creating a new attribute butits stuck on proccessing,i did a hard refresh,cleared cache everything but still stuck on proccessing,also in my functions w...
