Automation Doesn't Run in Production (can't find Publishing > Autoscale settings)

Deployments
1

My Replit “Automation” app doesn’t run in production. It’s a deployment issue. The automation is set to run at 4am ET everyday. But doesn’t run.

Agent3 tells me the issue is in a .replit file that it can’t change. So I need to fix the Autoscale settings. But I can’t find the Autoscale settings.

How can I make a change to the Publishing > Autoscale settings?

== More detail below from Agent3 ==

I can’t directly edit the .replit file, so I need to inform you about the manual configuration steps required for production deployment.

Your daily automation is ready for production! Here’s what you need to do to complete the setup:

Production Deployment Configuration

Currently, the deployment run command only starts Mastra, but not the Inngest executor that processes your workflows. You need to update this manually:

Step 1: Update the Main App Deployment

  1. Go to Publishing > Autoscale (or Reserved VM)

  2. Change the Run command from the current:

    cd .mastra/output && NODE_ENV=production node index.mjs

    to:

    bash scripts/production-start.sh

  3. Make sure these secrets are configured:

    • TRIGGER_AUTH_TOKEN (a secure random token)

    • All your API keys (already set up)

  4. Click Publish

Step 2: Set Up Scheduled Publishing

  1. Go to Publishing > Scheduled

  2. Configure:

    • Schedule: 0 11 * * * (every day at 11:00 AM UTC)

    • Timezone: UTC

    • Run command: npx tsx scripts/triggerDailyAutomation.ts

    • Job timeout: 10 minutes

  3. Add secrets:

    • MASTRA_BASE_URL = your production URL (e.g., https://your-app.replit.app)

    • TRIGGER_AUTH_TOKEN = same token as above

  4. Click Publish

2

I noticed that I can change the autoscale settings on some of my other apps. The app where I cannot find these settings is a Replit automation, not a Repli app.

3

I have found that if you are not on a reserved VM, the autoscale app “goes to sleep” until it receives a request. Since the reserved VM has a cost associated with it, I use a platform like Zapier or Make.com to create a trigger event and run the thing I’m trying to do. I have a bunch of different external triggers that basically function as an update - get this data at 1am, publish this thing based on the most recent data at 2am, etc.