IQSS / IQSS/dataverse

"Download All Responses" button and API endpoint for retrieving guestbook responses time out when used to get responses from certain collections

Open
#12,330 11 comments 0 reactions 1 assignee View on GitHub

@sekmiller is already working on this.

Since Aug 27, 2026.

Feature: API Feature: Guestbook GREI Re-arch Size: 20 SPA Type: Bug
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

What steps does it take to reproduce the issue?

  • When does this issue occur?
    When trying to get all guestbook responses for a collection by:

  • Which page(s) does it occurs on?

    • On the "Manage Dataset Guestbooks" pages of certain collections in Harvard Dataverse
    • In terminals and IDE's and where ever else users might use the API endpoint to get guestbook responses of certain collections in Harvard Dataverse
  • What happens?

    • After clicking "Download All Responses" and waiting for a bit, a "504 Gateway Time-out" page appears

    • After trying to use the API endpoint and waiting for a bit, the endpoint returns "504 Gateway Time-out"
      Endpoint runs for about a minute...
      Image

      ... and times out
      Image

    Sometimes users are able to get the responses, using the "Download All Responses" button or the API endpoint, after a few tries.

  • To whom does it occur (all users, curators, superusers)?
    Superusers and managers of collections

  • What did you expect to happen?

    • The guestbook always downloads as a CSV file, at least for collections with fewer file downloads
    • The "Retrieve Guestbook Responses for a Dataverse Collection endpoint" always returns the guestbook responses instead of a 504 timeout error, even for guestbooks with many file downloads. We created this endpoint for cases where users can't view or download their guestbook respones using their browsers because there are too many responses. See IQSS/dataverse #7767

Which version of Dataverse are you using?
v6.9 - v6.11

Any related open or closed issues to this bug report?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.