Hi. I need help diagnosing a permissions issue after yesterday’s Railway outage and recovery.

My Directus instance is back online and the content endpoints work publicly:

/items/dialogos?fields=.

/items/dialogos_textos?fields=.

Both return JSON correctly in incognito.

However, all public assets are now returning 403, for example:

/assets/f300c194-ae9e-4dbe-9094-257a87d1baf2

Error:

"You don't have permission to access collection "directus_files" or it does not exist. Queried in root."

This broke all images, PDFs, and file links across the public site.

Context:

• Yesterday Railway had a major outage affecting my Postgres/Directus services.
• Postgres crash-looped and Directus was stuck initializing, then both recovered after redeploy.
• During recovery, I attempted to create a backup through the Directus API.
• The backup successfully exported items/schema/directus_files metadata, but asset downloads returned 403.
• I then reviewed Public Policy permissions in Directus.
• Public Policy currently has Read enabled for the content collections and directus_files.
• But /assets/:id still returns FORBIDDEN publicly.

I need help identifying the precise Directus permission/state causing public assets to be blocked, without making further destructive changes.

Could this be caused by directus_files permissions, public role/policy assignment, system collection access, or a Directus 11 policy state issue after the outage?

Please advise the safest exact fix.