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.

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

BulkExport Reuse does not return same Job Id when a POST and then a GET is used #5157

Open
LalithE opened this issue Aug 1, 2023 · 0 comments · Fixed by #5161
Open

BulkExport Reuse does not return same Job Id when a POST and then a GET is used #5157

LalithE opened this issue Aug 1, 2023 · 0 comments · Fixed by #5161
Assignees
@LalithE

Comments

@LalithE
Copy link
Contributor

LalithE commented Aug 1, 2023 •
edited

Describe the bug
The reuse functionality does not return the same job Id for a bulk export task that has been requested with POST and then a GET export.

Steps to Reproduce
It shows up when somebody issues a POST/GET request for a bulk export job, and then uses a GET/POST to request the same job over again. Previously, it would have created a new job ID and not utilized the reuse function from bulk export. This fix remediates that.
@LalithE LalithE self-assigned this Aug 1, 2023
@LalithE LalithE linked a pull request Aug 2, 2023 that will close this issue
bulkExportReuse with POST and GET #5161
Merged
@LalithE LalithE changed the title BulkExport Reuse does not return same Job Id BulkExport Reuse does not return same Job Id when a POST and then a GET is used Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LalithE LalithE

Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@LalithE