8000 Sporadic timeouts in API method that seems to finish · Issue #58978 · vercel/next.js · GitHub
[go: up one dir, main page]
Skip to content

Sporadic timeouts in API method that seems to finish #58978

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
hbenl opened this issue Nov 27, 2023 · 2 comments
Closed
1 task done

Sporadic timeouts in API method that seems to finish #58978

hbenl opened this issue Nov 27, 2023 · 2 comments
Labels
bug Issue was opened via the bug report template. Runtime Related to Node.js or Edge Runtime with Next.js. stale The issue has not seen recent activity.

Comments

@hbenl
Copy link
hbenl commented Nov 27, 2023

Link to the code that reproduces this issue

https://github.com/replayio/delta

To Reproduce

The linked repository contains an app with an API for up-/downloading and comparing screenshots in test runs that is called in a GitHub CI workflow. Running that workflow will call the API dozens of times and some of those calls time out (but usually succeed when retried).
Furthermore there's a web app that uses the API to download the screenshots and that also times out sporadically.
Note that the app is deployed on Vercel.

Current vs. Expected behavior

Current: sporadic API timeouts
Expected: no API timeouts

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #99~20.04.1-Ubuntu SMP Thu Nov 2 15:16:47 UTC 2023
Binaries:
  Node: 18.18.2
  npm: 9.8.1
  Yarn: 1.22.18
  pnpm: 8.6.7
Relevant Packages:
  next: 14.0.3
  eslint-config-next: 13.0.7
  react: 0.0.0-experimental-ee8509801-20230117
  react-dom: 0.0.0-experimental-ee8509801-20230117
  typescript: 4.9.4
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Middleware / Edge (API routes, runtime)

Additional context

Here's the log from one uploadSnapshotVariants.ts API request that timed out:

START RequestId: 3225c3dc-fe9a-4375-889a-a8d0e21eb78a Version: $LATEST
2023-11-25T19:44:36.592Z	3225c3dc-fe9a-4375-889a-a8d0e21eb78a	INFO	Finding most recent snapshots for branch \"main\" and run 2068320
2023-11-25T19:44:36.687Z	3225c3dc-fe9a-4375-889a-a8d0e21eb78a	INFO	Inserting Snapshot for Project replay
2023-11-25T19:44:36.742Z	3225c3dc-fe9a-4375-889a-a8d0e21eb78a	INFO	Inserting SnapshotVariant for Snapshot 463692
2023-11-25T19:44:36.783Z	3225c3dc-fe9a-4375-889a-a8d0e21eb78a	INFO	Inserting SnapshotVariant for Snapshot 463692
2023-11-25T19:44:36.835Z	3225c3dc-fe9a-4375-889a-a8d0e21eb78a	INFO	Done!
2023-11-25T19:45:36.363Z 3225c3dc-fe9a-4375-889a-a8d0e21eb78a Task timed out after 60.06 seconds

END RequestId: 3225c3dc-fe9a-4375-889a-a8d0e21eb78a
REPORT RequestId: 3225c3dc-fe9a-4375-889a-a8d0e21eb78a	Duration: 60061.61 ms	Billed Duration: 60000 ms	Memory Size: 1024 MB	Max Memory Used: 83 MB

Note that this line was apparently executed and the handler tries to send a response immediately after that but timed out instead.
@hbenl hbenl added the bug Issue was opened via the bug report template. label Nov 27, 2023
@github-actions github-actions bot added the Runtime Related to Node.js or Edge Runtime with Next.js. label Nov 27, 2023
@nextjs-bot
Copy link
Collaborator

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

@nextjs-bot nextjs-bot added the stale The issue has not seen recent activity. label May 25, 2025
@nextjs-bot
Copy link
Collaborator

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!

@nextjs-bot nextjs-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Issue was opened via the bug report template. Runtime Related to Node.js or Edge Runtime with Next.js. stale The issue has not seen recent activity.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hbenl @nextjs-bot
0