-
Notifications
You must be signed in to change notification settings - Fork 104
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
504 Gateway Time-out #881
Comments
Sorry for the late reploy. Is it working with other address? It could be that addresses with a lot utxos could lead to timeouts when graphQL is running on smaller servers. |
Hi @Kammerlo I dont think this is related necessarily to the number of UTXO's. E.g. this address only has 9 txs and times out: curl --location 'https://explorer.cardano.org/graphql/' --header 'Content-Type: application/json' --data '{"query":"query {\r\n paymentAddresses(\r\n addresses: [\r\n \"addr1qygcsk5l4xh3y3m8j8akv93yyun06wfadrr3de02vj80xyg33pdfl2d0zfrk0y0mvctzgfexl5un66x8zmj75eyw7vgsfpl75e\"\r\n ]\r\n ) {\r\n summary {\r\n assetBalances {\r\n asset {\r\n assetId\r\n }\r\n quantity\r\n }\r\n }\r\n }\r\n}\r\n","variables":{}}' or this one with 19 txs: curl --location 'https://explorer.cardano.org/graphql/' --header 'Content-Type: application/json' --data '{"query":"query {\r\n paymentAddresses(\r\n addresses: [\r\n \"addr1q8034em76n4qyhfrexv8j349gpcr5904cc4fm9vf7le59wxlrtnha482qfwj8jvc09r22srs8g2lt332nk2cnalng2uqnnqh77\"\r\n ]\r\n ) {\r\n summary {\r\n assetBalances {\r\n asset {\r\n assetId\r\n }\r\n quantity\r\n }\r\n }\r\n }\r\n}\r\n","variables":{}}' |
@cryptosystems6300 This issue doesn’t appear to be related to GraphQL, but rather a server problem. Please note that the GraphQL instance behind that explorer is not intended for third-party use and will be decommissioned in the future. |
Summary
504 Gateway Time-out on Graphql requests on Cardano Graphql 8.1.0
Steps to reproduce the bug
Actual Result
Expected Result
Actual balance object
Environment
mainnet, Cardano Graphql 8.1.0
Platform
Platform version
No response
Runtime
Runtime version
No response
The text was updated successfully, but these errors were encountered: