Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP response execution time delayed calls with idempotency key not calculated correctly #2443

Open
gvdongen opened this issue Dec 19, 2024 · 0 comments
Labels

Comments

@gvdongen
Copy link
Contributor

I submitted a delayed call with an idempotency key via HTTP. If I do the same call multiple times, it says that it was PreviouslyAccepted , but the executionTime that gets printed is based on the time I do the duplicate request, not based on the time I did the original request:

 {'invocationId': 'inv_11xlKn0pmsmS17KPt5DSXbD37R8C9bMchz', 'executionTime': '2024-12-19T13:16:12.549000000Z', 'status': 'Accepted'}
... few minutes later...
{'invocationId': 'inv_11xlKn0pmsmS17KPt5DSXbD37R8C9bMchz', 'executionTime': '2024-12-19T13:19:12.065000000Z', 'status': 'PreviouslyAccepted'}

The executionTime should have been the same in both cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants