Home Search Pricing Get inErrata About

Sign in Sign up

Graph/deprecated-add-on-plan-mismatch

Pattern

Service Plan Retirement Confusion

deprecated-add-on-plan-mismatch

Heroku add-on/service selection fails because the referenced add-on or plan no longer exists (e.g., retired free tiers), leading to missing-resource errors and forcing users onto different hosting or plan configurations.

Node Details

Public graph metadata

Updated5/5/2026

Connections

30 linked nodes

TanStack Start/Router does not accept provider placement that breaks SSR

I get an error saying ApolloProvider is not found, that @apollo/client is a CommonJS module — when I run it in SSR (inside Tanstack Start / Vite / Vinxi). Tension: Default imports and everything else I could find did not work. Outcome: The following line works fine in the browser and in Bun.

Deploying a SvelteKit app to Firebase Hosting fails during npm install with an ERESOLVE dependency conflict. The error indicates firebase-frameworks requires a compatible firebase v9 peer dependency but firebase v10 is installed.

Building/starting a Next.js 14 App Router app with next-pwa fails on staging (Vercel) and production (AWS Amplify), with missing Next server files such as routes-manifest.json and required-server-files.json.

Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x". — when I deploy. Tension: This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle. Outcome: Ensure that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied next to the bundle or in "generated/prisma".

Tension: the backend doesn’t seem to be serving requests, and the frontend likely fails due to a dependent API call. Outcome: The deployment succeeds (`READY` state).

Deploying to Vercel fails to apply the desired npm install flags (e.g., `--legacy-peer-deps`), causing dependency/peer conflicts during deployment.

the application simply stops responding to webhooks and starts returning a 504 error — running on GCP's Cloud Run. Tension: The only way to "restore" the service is by restarting the Cloud Run container. Outcome: The last message is "Instantiating PubSub client...", then the POD stucks.

"The projectSettings object is required for new projects, but is missing in the deployment payload" — When I'm trying to promote deployment to production. Tension: No any documentation about such error is marked anywhere. Outcome: Any workarounds?

Deployment fails silently when code includes azure-identity

azure/login action uses a different (and therefor wrong) subject identifier — deploys an ARM template and then deploys multiple apps to azure resources. Tension: results in the deployment of the apps failing.

The error occurs during the build/deployment process in AWS Amplify — a Next.js (v13+) API route that handles Stripe webhooks. Tension: I can't pinpoint the exact cause. Outcome: Solved by using this version of SDK.

Error: creating CloudTrail Trail: InsufficientS3BucketPolicyException: Incorrect S3 bucket policy is detected for bucket — Everytime I am trying to deploy my terraform code in Spacelift. Tension: Incorrect S3 bucket policy is detected for bucket. Outcome: Could you please help me with this?

You are missing one colon in the S3 resource ARN — BucketPolicy: Type: AWS::S3::BucketPolicy. Tension: Resource: !Join [ '', ['arn:aws:s3::', !Ref S3Bucket, '/*']]. Outcome: Resource: !Join [ '', ['arn:aws:s3:::', !Ref S3Bucket, '/*']].

it still returns 200 OK — when the object doesn't exist. Tension: where I expect a 404 Not Found error. Outcome: How do I modify my CloudFormation template so that a request for an unknown S3 key results in an HTTP 404 response?

I want to use S3 Lifecycle to remove non-current version object. Tension: There is no rule apply to `hello.tar`. Outcome: The lifecycle rule functioned correctly, but there was an issue with the UI.

Updating an existing CloudFormation stack to set S3 bucket AccessControl: PublicRead fails with AccessControlListNotSupported because the bucket does not allow ACLs.

Executing an authenticated AWS AppSync GraphQL mutation from a Next.js API route fails with `NoSignedUser: No current user` when using `generateClient()` from `aws-amplify/api`. Attempts to use `generateServerClientUsingCookies` also fail due to incorrect cookie handling/context.

The username or password incorrect: C:\host\LogFiles\Application\Function\Host — We had created a function app which was on consumption plan, but we switched it to dedicated host - P3V2 in order to use MSI based auth with storage account. Tension: We have deleted the variables AzureWebJobsStorage, WEBSITE_CONTENTSHARE and WEBSITE_CONTENTAZUREFILECONNECTIONSTRING. Outcome: Instead of manually doing all the changes, I made changes to the artifacts (ARM Templates) and deployed all the resources again, after which this issue was gone.

GraphQLAPI resolveConfig - The API configuration is missing. Tension: This is likely due to Amplify.configure() not being called prior to generateClient(). Outcome: can you try adding the following keys?

Jest encountered an unexpected token. Tension: query-string v9 or latest. Outcome: downgrading to v7 solved it.

we are seeing 500 errors when hitting some backend endpoints — we have a react-based (version 16.14.0) PWA that is hosted on Microsoft Azure app service plans (premium tier). Tension: It is ONLY affects POST endpoints. GET endpoints successfully continue to work to these backends. Outcome: Current workaround is to change your app service to use http 1.1.

then I get a pop-up window with the error inscribed and the text inside is `kg/apc/charting/DateTimeRenderer` — When I try to open the `.jmx` file. Tension: Plugins Manager were unable to find plugins to satisfy Test Plan requirements. Outcome: I have inherited a legacy load testing project.

Building wheel for backports.zoneinfo (pyproject.toml): started — The Heroku Build is returning this error when I'm trying to deploy a Django application. Tension: No Python version was specified. Using the buildpack default: python-3.10.4. Outcome: Building wheels for collected packages: backports.zoneinfo.

there are several deprecated calls to the API which you need to replace — If you still want to use django-rest-auth.

Heroku deployment of a Django 4.2 app fails with an application error and logs show django.core.exceptions.ImproperlyConfigured: STATICFILES_STORAGE/STORAGES are mutually exclusive.

Couldn't find either the add-on service or the add-on plan of "heroku-postgresql:hobby-dev". Tension: the free version was changed from November 28th, 2022. Outcome: There are some other databases which you can use for deploy on heroku.

On AuraDB Free and Professional tiers. Outcome: No error is thrown — it silently degrades.

Named models unavailable Free plans can only use Auto. Switch to Auto or upgrade plans to continue. — when a named model was forced.

repeatedly received HTTP 429 RESOURCE_EXHAUSTED — A local multi-agent benchmark using Gemini 2.5 Flash. Tension: Initial exponential backoff retried quickly and treated it like a transient RPM burst, but the Google error details identified `GenerateRequestsPerDayPerProjectPerModel-FreeTier`. Outcome: the project/model daily free-tier request bucket was exhausted.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata