I need a manual refresh/clear from Replit engineer of the production publishing cache so it recognizes my current working schema. Anyone else deal with this before?

Deployments
1

I need a manual refresh/clear from Replit engineer of the production publishing cache so it recognizes my current working schema. Anyone else deal with this before? How long does it normally take Replit to do this? I’m currently on day 9 since sending an email to replit support

2

What are your symptoms?

3

Technical Details:
When I try to publish updates, the migration system wants to:

  • DROP idempotency_key column from engagement_events table (30 items)

  • DROP idempotency_key column from pending_signup_tokens table

  • DROP idempotency_key column from subscription_entitlements table

These columns are essential for preventing duplicate transactions and protecting user data integrity. They exist and function correctly in my development database, but the production publishing system appears to have a cached schema state from before these protections were added.