-
Notifications
You must be signed in to change notification settings - Fork 107
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.
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
Server error time out #174
Comments
I am having the same issue. When initiating, I get an output of "Started parsing the file under job_id " After an extended period of time, I get an output of This has been an ongoing issue all day. Has the issue been examined, @jerryjliu @Disiok and colleagues? |
@rwclayton @jes252 if you can provide some way to reproduce, happy to take a look |
I had same issues during same time period as @rwclayton. Some status mechanism on the cloud site would be helpful. Very frustrating when trying to determine if a coding issue or a server issue. |
It started working again
…On Tue, May 14, 2024 at 11:44 AM Logan ***@***.***> wrote:
@rwclayton <https://github.com/rwclayton> @jes252
<https://github.com/jes252> if you can provide some way to reproduce,
happy to take a look
—
Reply to this email directly, view it on GitHub
<#174 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXLTNXKO3PG45547Y4DF4IDZCIWNZAVCNFSM6AAAAABHRFKGJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJQGU3DONJXGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
both inside the application and when using the API the server times out.
The text was updated successfully, but these errors were encountered: