Forge app (Jira) with REST endpoints exposed via the “Expose a REST API” feature, backed by a core:function handler. We test them with Jest E2E tests — the HTTP client does a single fetch per request, no retry logic, and tests run sequentially. Locally it’s fine, but in CI a single DELETE sometimes…

Quick update — we found a deterministic cause in our case. The duplicate invocation is triggered by calling internalMetrics (counter incr/decr) inside the handler’s request path: every endpoint that calls it is invoked twice, every endpoint that doesn’t is invoked once. Removing the metrics call mak…

Hi @emrekaraduman , Because you indicated this is intermediate, I suspect this is due to Forge’s at-least once delivery semantics for Forge function invocations. Here’s some additional information I dug up using AI - it looks OK to me: Why duplicate invocations happen Forge runs on a distributed, …

[image] dmorrow: You may also want to upvote/follow FRGE-391 which tracks at-least-once delivery concerns for Forge functions. Hi @dmorrow , This seems like a hallucination.

Deletes are easy to handle, but I can’t be the only one who thinks that double processing for REST APIs is not acceptable. Using Forge KVS – which has a limit of 4k requests per minute – to deduplicate requests is yet another burden on the developer and yet another case in which we have to use the …

[image] dmorrow: You may also want to upvote/follow FRGE-391 which tracks at-least-once delivery concerns for Forge functions. @dmorrow , I don’t think FRGE-391 is about this topic. Wrong link?

This double processing seems rather scary and a big burden on developers. The proposed solution with first a get then a delete also seems optimistic at best. I’ve tried to use the Forge KVS in the past and if two read/write combinations happen in a narrow window, I believe it was around 300ms, the s…

I think it would be good to identify the two different distinct issues in this thread: AWS Lambda idempotency requirement Dealing with Idempotency in your code The first one is well documented: AWS simply does not offer only-once execution for Lambda functions. Not even for HTTP requests. The Lam…

If there are multiple invocations of endpoints, this will be expensive to deal with for vendors. We have to pay per function call with Forge/lambda, and Atlassian shoves extra costs on us. A second, and possibly more urgent concern is about rate limits. If our functions get called multiple times …

@marc , @AndreasEbert , yes, I missed the incorrect link to FRGE-391 - it was an AI confabulation so I’ve removed it to avoid further confusion. @marc , I see your point about the additional impact on costs and rate limits, but I assume the percentage of superfluous invocations is negligible. @remie …

[image] dmorrow: focussing on tactics to deal with this in app code For the record: I never said this has to be solved in app code. It can also be solved by Atlassian, for instance by following AWS recommendation to implement response caching: You can implement idempotency in Lambda functio…

Does Forge invoke an exposed REST API endpoint more than once per request?

Forge

marc June 7, 2026, 9:02am 3

Hi @dmorrow ,
This seems like a hallucination.