Assigned
Status Update
Comments
bs...@google.com <bs...@google.com>
ds...@google.com <ds...@google.com> #2
Hello,
To assist us in conducting thorough investigation, we kindly request your cooperation in providing the following information regarding the reported issue:
- Has this scenario ever worked as expected in the past?
- Do you see this issue constantly or intermittently ?
- If this issue is seen intermittently, then how often do you observe this issue ? Is there any specific scenario or time at which this issue is observed ?
- To help us understand the issue better, please provide detailed steps to reliably reproduce the problem.
- It would be greatly helpful if you could attach screenshots of the output related to this issue.
Your cooperation in providing these details will enable us to dive deeper into the matter and work towards a prompt resolution. We appreciate your assistance and look forward to resolving this issue for you.
Thank you for your understanding and cooperation.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Unable to consume pretrained-w2-v1.2-2022-01-28 version of W2 Parser Model. Every time I send a request to the model it brings up the below responses.
{
"error": {
"code": 503,
"message": "StubsClientChannel::Cancel called. Cancelling request.; ucaip_endpoint = \"projects/188558982164/locations/us-central1/endpoints/3784932439177035776\"; Failed to execute processor element: cde-clara-pipeline_0_clara_extraction_element; Failed to execute processor element: cde-clara-pipeline_0_calibration_task; Failed to execute processor element: static_ensembling_element; Failed to execute processor element: enrichment_element; Failed to execute processor element: normalization_element; Failed to execute processor element: merge_documents_element; Failed to execute processor element: update_page_anchor_element; Failed to execute processor element: reset_entity_ids_element; At least one processor element failed during parallel execution.; Process document failed during processing. event_id = \"EG-lY8WWOo21sgfGlpqwDw\"",
"status": "UNAVAILABLE"
}
}
{
"error": {
"code": 503,
"message": "Took too long to respond when processing endpoint_id: 3784932439177035776, deployed_model_id: 487716969802366976.",
"status": "UNAVAILABLE"
}
}
{
"error": {
"code": 503,
"message": "The service is currently unavailable.",
"status": "UNAVAILABLE"
}
}
What you expected to happen:
1. I want the pretrained-w2-v1.2-2022-01-28 version of the W2 parser model up and running.
2. Reason for the model behavior, so that I can be prepared for the future.
Steps to reproduce:
1. Send a request to pretrained-w2-v1.2-2022-01-28 version of W2 parser model.
Other information (workarounds you have tried, documentation consulted, etc):