Scheduled jobs require more seats?

Hello :wave:

Trying to add a scheduled job to a project, but I get a strange error:

This job has been blocked because no user seats are available on your plan. Please purchase more user seats to continue building.

Notice the “Triggered by: unkown” in the top right - not sure if this is the cause of the problem.

We’re on a paid plan with 4 users.

The setup:

  version: 2
      - schedule:
          cron: "* * * * *"
                - master
                - develop
                - patch-and-audit-vulnerabilities-in-projects
      - audit-vulnerabilities

Yes, scheduled workflows will count as a seat on your plan. If you’re already at the max users for you plan you’ll need to increase your seat count. You can read more about active users here.

If I want to run multiple scheduled workflows, will I have to buy a user seat pr schedule? Or pr workflow? Pr Project? Or will this user be used automatically for all scheduled jobs?

It seems like a very weird requirement/way of doing things to me. Fair enough (maybe) if you want scheduled workflows to be an additional ad-hoc paid feature for 15$/month, but this implementation of it is not logical to me. :slight_smile:

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.