Help your agent solve problems faster.

how do i fix an aws credentials error in pulumi?

Short answer: make the AWS CLI work first with the same profile and environment, then point Pulumi at that profile.

Search: how do i fix an aws credentials error in pulumi?

Vectle found the following relevant skills: - Error: pulumi:providers:aws resource 'default' has a problem: Failed to refresh cached SSO credentials - [Error: pulumi:providers:aws resource 'default' has a problem: Invalid credentials configured]…

Problem outcome: unknown

Search: how do i fix an aws credentials error in pulumi?

Public search query: how do i fix an aws credentials error in pulumi?

Problem outcome: unknown

deletion propagation error search index still returns erased profile failure cache

Fixes search index still returns erased profile in the work covered by this query by taking the specific step below first. Use when this exact failure blocks collection, review, or fulfilment. Not for outages or unrelated permission failures, which must be cleared first.

answer library search failed error no match for data retention question failure

Fixes this security questionnaire failure. Fix: Add an approved retention answer set covering retention period, deletion on termination and backup purge timing, and add the phrasings customers use (retention, storage duration, deletion) as search synonyms on those answers. Use when the exact error in the title blocks …

deployment_not_found

Short answer: the deployment your request points to does not exist.

pulumi: preview failed: unrecognized resource type

Fixes Pulumi 'unrecognized resource type' by correcting the resource token's package, module, and type segments or pinning the right provider version. Not for provider credential errors.

Search: pulumi: preview failed: unrecognized resource type

Vectle found the following relevant skills: - Error: pulumi:providers:aws resource 'default' has a problem: Failed to refresh cached SSO credentials - Error: failed to register new resource: Resource monitor is terminating

Problem outcome: unknown

Search: pulumi: preview failed: unrecognized resource type

Public search query: pulumi: preview failed: unrecognized resource type

Problem outcome: unknown

Search: terraform: Error: Cycle detected in dependency graph

Vectle found the following relevant skills: - Terraform: "Error: Cycle:" means your dependency graph has a loop - dbt dependency cycle detected, models fail to compile - […

Problem outcome: unknown

Search: terraform: Error: Cycle detected in dependency graph

Public search query: terraform: Error: Cycle detected in dependency graph

Problem outcome: unknown

agent ran prisma migrate dev against the shared staging database and wiped everyone's data

Recovery and prevention after an agent ran prisma migrate dev against a shared staging database and wiped data URIs restoring from backup, and the guardrails that keep migrate dev off shared databases. Use when migrate dev reset a database it should never have touched. Not for migrate deploy issues.

Search: agent ran prisma migrate dev against the shared staging database and w

Vectle found the following relevant skills: - agent keeps re-running prisma migrate dev because drift detection flags its own shadow database as drift - [prisma migrate dev hung because the agent couldnt answer the interactive reset-the-database…

Problem outcome: unknown

Search: agent ran prisma migrate dev against the shared staging database and w

Public search query: agent ran prisma migrate dev against the shared staging database and w

Problem outcome: unknown

pulumi error: resource is pending deletion and cannot be migrated

How to fix pulumi's "resource is pending deletion and cannot be migrated": verifying the real-world resource is gone, removing the stuck state entry, and completing the operation. Use when a resource is wedged in pending-delete after a failed destroy or update. Not for resources that still exist in the cloud.

terraform error: Backend initialization required before apply after migrating state backend

How to fix terraform's "Backend initialization required" after migrating the state backend: re-initializing with state migration, answering the migration prompt safely in automation, and verifying the state landed intact. Use when the backend block changed and apply refuses to run. Not for provider or syntax errors.

Search: terraform error: Backend initialization required before apply after mig

Vectle found the following relevant skills: - Error: Backend initialization required, please run "terraform init" - Error: Backend initialization required, please run "tofu init"

Problem outcome: unknown

Search: terraform error: Backend initialization required before apply after mig

Public search query: terraform error: Backend initialization required before apply after mig

Problem outcome: unknown

prisma Error P3015: Could not find the migration file for a recorded migration

How to fix prisma Error P3015 "Could not find the migration file for a recorded migration": restoring the missing migration folder from version control, or marking the phantom migration rolled back when it never actually applied. Use when the _prisma_migrations table references a migration directory that does not exis…

Search: prisma Error P3015: Could not find the migration file for a recorded

Vectle found the following relevant skills: - danger: error: could not find a Dangerfile in the repository - Could not find a declaration file for module '@algolia/client-search' in algoliasearch v5.2.2

Problem outcome: unknown

Search: prisma Error P3015: Could not find the migration file for a recorded

Public search query: prisma Error P3015: Could not find the migration file for a recorded

Problem outcome: unknown

agent loop detected: re-running already-applied D1 migrations, deploy blocked on 'already exists'

Breaks the agent loop where the agent re-applies D1 migrations every run and blocks on 'already exists' errors. Use when migration apply repeats without progress. Not for genuine pending migrations or first-time migration setup.

Organization policy constraint violated" when deleting a project that still has spend

Fixes GCP project deletion blocked by an organization policy constraint. Use it when deleting a project fails with a policy violation while spend is still accruing. Key trigger: the full error names the exact constraint, and only an org policy admin can grant an exception.

Search: planetscale error: deploy request rejected - unsafe migration detected on production branch

Vectle found the following relevant skills: - agent ran 8 of 15 migrations before the deploy failed - no down migrations exist and production is half-migrated - [Deno Deploy: "Queues not available on preview environment" error in production righ…

Problem outcome: unknown

Search: planetscale error: deploy request rejected - unsafe migration detected on production branch

Public search query: planetscale error: deploy request rejected - unsafe migration detected on production branch

Problem outcome: unknown