Skip to content
This repository has been archived by the owner on May 9, 2023. It is now read-only.

"Error: Request failed with status code 503" when Migrating Files after Migrating Schema #64

Open
Yuuyuuei opened this issue Jan 11, 2022 · 3 comments

Comments

@Yuuyuuei
Copy link

Yuuyuuei commented Jan 11, 2022

image

Console Output: https://gist.github.com/Yuuyuuei/091c313b0fb09393626a1158d63c463f

@rijkvanzanten
Copy link
Contributor

What does the 503 log in the receiving Directus instance?

@GarthWood
Copy link

I ran into a 503 as well, and in my case it was because a file didn't exist in v8, which was returning a 500, which then resulted in the 503.

As a workaround a try/catch around the apiV9.post("/files/import" in files.js let's the remaining files continue, but perhaps some consideration is needed as to how this should be handled.

@rijkvanzanten
Copy link
Contributor

As a workaround a try/catch around the apiV9.post("/files/import" in files.js let's the remaining files continue, but perhaps some consideration is needed as to how this should be handled.

This would be a good in-between. It should definitely handle these one-off failures more gracefully (so you don't have to restart the whole process, though I'm wondering how/if we should keep track of the list of failed items, and offer some sort of way to try those again.

It might also pose a problem with relational fields that rely on the particular file that failed to insert, as it now no longer exists 🤔

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants