#cron-jobs

Mike Tickstem **Update:** Tickstem now includes **status pages** that auto-generate from your uptime monitors and heartbeat checks --- no manual ***"we're investigating"*** posts needed. The page reflects your actual monitor state in real time. If your monitors are green, the page is green. If an endpoint goes down, the page updates automatically. You get a public URL at `https://tickstem.dev/status/your-slug` --- shareable with users, **no separate service needed**. Works well alongside Vercel deployments: monitor your API routes, set up a heartbeat on your background jobs, and your status page stays current without any manual updates. Free tier includes 5 monitors and a status page. https://tickstem.dev

Mike Tickstem **Update:** Tickstem now has an **MCP server** --- if you use Claude Code or Cursor alongside your Vercel projects, your AI assistant can register cron jobs, create uptime monitors, and set up heartbeat checks directly from the editor. **Remote option (no install)**: connect via https://mcp.tickstem.dev/mcp --- works with any MCP-compatible client. **Local binary option**: go install github.com/tickstem/mcp/cmd/tsk-mcp@latest Same API key you're already using. Useful when you're scaffolding a new Vercel project and want the agent to wire up monitoring as part of the build.

system If you're having trouble deploying an Express app, this guide can help. https://vercel.com/guides/using-express-with-vercel You can also ask v0 for suggestions tailored to your own project setup.

system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/domains/troubleshooting

Pauline P. Narvas Hey, Brightpixels! Welcome to the Vercel Community For anyone else reading this, this is about the `live` property from the Vercel REST API, docs here: https://vercel.com/docs/rest-api/projects/retrieve-a-list-of-projects From my understanding, the `live` property appears to be an internal state that tracks whether your production deployment is actively serving traffic, which is separate from the `paused` state. When a project is paused, both `paused: true` and `live: false` are set. It looks like the unpause endpoint might not be properly restoring the `live` state in your case. To resolve this: * Try triggering a new production deployment as this often resets the project state * If that doesn’t work, try using the Vercel Dashboard to resume the project (Settings → Resume Service button) Regarding your cron jobs - yes, if live: false, your cron jobs won’t execute since they only run on active production deployments.