Cypress getting crashed while uploading QRDA III

[sudhir-nair]

It is giving following error.
Server Error
Something went wrong with this request. This is likely a problem with Cypress rather than a mistake on your part. Please find attached xml file just rename it to .xml.

File is a QRDA III xml for CMS111

QRDA3 (1).txt

[ssayer]

Sudhir,

Can you confirm you're on the latest release (Alpha 6)?

-Sam

[sudhir-nair]

Yes am using Alpha 6

[sudhir-nair]

Am unable to retry upload of QRDA III file now.Seems like i need to create a new product and reprocess complete data.

[ssayer]

Sudhir,

If you’re going to lose a non-trivial amount of work, we can try to find a workaround once we’re done testing your file.

-Sam

From: sudhir-nair notifications@github.com
Reply-To: projectcypress/cypress reply@reply.github.com
Date: Friday, June 3, 2016 at 10:35 AM
To: projectcypress/cypress cypress@noreply.github.com
Cc: "Sayer, Sam" ssayer@mitre.org, Comment comment@noreply.github.com
Subject: Re: [projectcypress/cypress] Cypress getting crashed while uploading QRDA III (#493)

Am unable to retry upload of QRDA III file now.Seems like i need to create a new product and reprocess complete data.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com//issues/493#issuecomment-223596014, or mute the threadhttps://github.com/notifications/unsubscribe/AAAeNYF0Zyy7OLVPPjQk3ibbNi5yoySwks5qIDvDgaJpZM4ItlN_.

[sudhir-nair]

It's fine...I can reprocess. Just let me know what went wrong.

[dczulada]

Thanks for pointing this out. There is a bug in Cypress that is preventing displaying the error message related to the file you uploaded.

The error in your file is related to the OBSERV id. The file you attached is still using the id "b9352e6d-c82d-424a-a1d3-05a1f3fbaed3" from the measures released in 2014. This id needs to be updated to "C71EF921-C721-477D-AB8A-14FB9A19C50D." I've uploaded a file making that change which should now work.

QRDA3.1.txt

[ssayer]

Sudhir,

This should be fixed in the latest beta1 release. If it is not, please reopen