30 days of Postman - Day 19

Hello to everyone!
Problem to run query on https://spotify-graphql-server.herokuapp.com/graphql. It repsonse status - 503

<!DOCTYPE html>
<html>

<head>
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<meta charset="utf-8">
	<title>Application Error</title>
	<style media="screen">
		html,
		body,
		iframe {
			margin: 0;
			padding: 0;
		}

		html,
		body {
			height: 100%;
			overflow: hidden;
		}

		iframe {
			width: 100%;
			height: 100%;
			border: 0;
		}
	</style>
</head>

<body>
	<iframe src="//www.herokucdn.com/error-pages/application-error.html"></iframe>
</body>

</html>

Hey @wirtaw,

Seems like a problem with herokuapp, I had sent this POST request a few days back and it was working well, but now we are getting this error. So, just wait for some official response.

Hey @wirtaw :wave:

Update: It seems to be working now, kindly test your request as well.

1 Like

I have the same issue: 503 Service Unavailable
What can I do?

Hi All, I am getting the same problem and this is the last thing to get my badge.

I have rebuilt, doubled checked and watched the video. Still 503.

Oh, and I have tried on multiple days at different times to rule out server maintenance…

Did anyone manage to find a solution to this? Still getting a 503 when posting this request.

Swapped out the server with a new one. Please pull changes from the collection for the latest instructions. Thanks for your patience :dove:

2 Likes

@jetison I have pulled the latest changes for Day 19 but am still getting the 503 Service Unavailable when submitting a Post request for URL https://spotify-graphql-server.herokuapp.com/graphql. If you replace the URL with this one https://joyce-spotify-graphql.herokuapp.com/graphql I get a valid response and 200 OK but my last test fails as its expecting URL https://spotify-graphql-server.herokuapp.com/graphql. Any ideas?

query getByArtist($name: String!) {

queryArtists (byName: $name) {

 name

 image

 albums {

     name

 }

}

}

With GraphQL Variables
{

“name”: “Bruno Mars”

}

Test that fails :
pm.expect(request.request.url.raw, ‘check url’).equals(“https://spotify-graphql-server.herokuapp.com/graphql”)

Hi @bleazier - it sounds like you have not pulled updates from the Day 19 parent collection. Once you do that, your collection will look like the parent collection, so the instructions will refer to the new URL and the test will assert that you have the new URL. Then, go through the challenge, and save your updates once your tests are passing locally.

If pulling updates becomes too confusing, you can instead re-fork the parent collection and start fresh.

HI All,
When I click Auto-fetch, it shows warning. Also, I clicked Send and it response status -503. It seems like there were some people going through this issue before. Anyone could help?

@rivierevo - our team just updated to a new deployment. Please pull the latest collection changes to see the new API.

1 Like

Hi @jetison. I can fetch the graphQL now. However, I cannot pass the final test due to the different URL. Kindly help me one more time in this case. Thank you!

Sorry for that oversight @rivierevo - I’ve reverted to the original URL (which has been fixed!). If you’re pulling changes again, it looks like a lot of updates as I was fixing formatting issues, but know to just use the original URL.

So sad to share with you that the former url https://joyce-spotify-graphql.herokuapp.com/ sends 404 response back :sweat_smile: It supposed to auto-fetch the schema, which I followed every step in the Documentation. I very appreciate your effort in helping me. I attached the screenshot when I tried opening the url directly here as well. Could you review and check the url once again? Thank you!


Oh @jetison I found out the issue here. This happened due to the url you attached in Documentation is different from the one it supposed to be ^^ . I enclosed the photos here for further comparison. I tried with this url and it worked actually https://joyce-spotify-graphql.herokuapp.com/graphql. I think the issue is resolved now. Thank you for your help :smiling_face_with_three_hearts:


Updated! Thanks for your sleuthing @rivierevo :mag:

1 Like