That restriction isn't coming from Railway. Your workspace has no restrictions on it, active or lifted, and exceed_storage_size_quota isn't a code we can produce.

It's coming from Supabase. Your pipeline-worker's claimNextJob call is hitting ygzmwhpchuzjrsqltdog.supabase.co, and Supabase is returning that message about its own project being restricted for exceeding a storage quota. The word "project" in the error means the Supabase project, not the Railway one, which is why upgrading here didn't change anything.

Check the Supabase dashboard for that project. You'll need to free up storage or upgrade on their side. Your Railway services are both deploying fine and you have no volumes attached, so there's nothing on our end holding you up.

Happy to look again if clearing it on Supabase doesn't fix the worker.