# Origin Automations Not Working

**URL:** <https://forum.cursor.com/t/origin-automations-not-working/169534>\
**Category:** Bug Reports\
**Tags:** origin, automations\
**Created:** [August 26, 2026, 12:34pm UTC](https://forum.cursor.com/t/origin-automations-not-working/169534 "2026-08-26T12:34:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![naquiroz](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/naquiroz/32/63523_2.png) [@naquiroz](https://forum.cursor.com/u/naquiroz)\
**Post date:** [August 26, 2026, 12:34pm UTC](https://forum.cursor.com/t/origin-automations-not-working/169534/1 "2026-08-26T12:34:18Z")

</div>

### Where does the bug appear (feature/product)?

Somewhere else…

### Describe the Bug

I’ve activated an automation in one of my origin repos, to run on a schedule, but they won’t run. When I try to test run them it says I need to connect or configure an SCM or something.

### Steps to Reproduce

1. Create an origin repo.
2. Add custom crontab to run every 30 minutes
3. wait or test run
4. What it fail

### Expected Behavior

The automation should run

### Screenshots / Screen Recordings

 ![IMG_8865.png](https://us1.discourse-cdn.com/cursor1/original/3X/8/a/8a382d3d6b28f33d70fe5a27f4255979d610d952.jpeg)

### Operating System

Other

### Version Information

Cloud Automation

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [August 26, 2026, 6:03pm UTC](https://forum.cursor.com/t/origin-automations-not-working/169534/12 "2026-08-26T18:03:27Z")

</div>

Hey @naquiroz, thanks for the report! This is a known limitation that we’re actively working on. Scheduled automations on Origin-hosted repos aren’t fully wired up yet for environment-backed automations, and the “connect your SCM account” message is misleading in this case.

In the meantime, two workarounds should work today: pointing the automation directly at a repo + branch (rather than selecting a saved environment), or running it against a GitHub-hosted repo.

---

<div class="post-metadata">

**Author:** ![naquiroz](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/naquiroz/32/63523_2.png) [@naquiroz](https://forum.cursor.com/u/naquiroz)\
**Post date:** [August 26, 2026, 6:56pm UTC](https://forum.cursor.com/t/origin-automations-not-working/169534/14 "2026-08-26T18:56:38Z")

</div>

How can I pick a branch on the automation?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [August 27, 2026, 8:22am UTC](https://forum.cursor.com/t/origin-automations-not-working/169534/19 "2026-08-27T08:22:36Z")

</div>

Hey @naquiroz!

The issue that was blocking scheduled automations on Origin-hosted repos has been fixed on our side, so automations that use a saved environment with an Origin repo now launch correctly.

If you edit the automation (or its environment) to point at one of your current repos, the schedule should start running.

To answer your question about picking a branch: when you create or edit the automation, choose the repository directly in the repo picker instead of selecting a saved environment, you can set the branch right there. Both paths should work now.