Cron jobs never created, and prevent full deploy

[cerilloderek]

A simple CRON job never gets created as an AWS eventbridge rule. I have AdministratorAccess with my IAM account.

export const licenseRenewalReminders = new sst.aws.Cron(
  'LicenseRenewalReminders',
  {
    schedule: 'cron(0 0 ? * 1 *)', // minute, hour, day of month, month, day of week, year
    // schedule: 'rate(1 minute)',
    job: 'core-cerillo-api/src/renewals.main',
    enabled: !$dev,
  }
);

Imported in my sst.config with /

    const licenseRenewalReminders = await import(
      './infra/licenseRenewalReminders'
    );
    console.log(licenseRenewalReminders);

If I try to cancel the deploy it never actually completes the cancel or even force cancel. I have to ctrl+D my way out of the shell and then sst unlock to try again. Weirdly it seems that once in a blue moon a cron job is created successfully, but I can't tell from any of the sst or pulumi logs what the magic trick is to get it to create. Creating CRON jobs was no problem a week ago on the same SST version 3.17.23. I tried upgrading sst version to the latest, but that also didn't seem to work.

[cerilloderek]

Found out that I was hitting the maximum number of rules for my aws sevice plan and that's why it was failing to create. Once I cleared some stale rules, I could deploy successfully. It would be nice if there was an indication of the error in sst, but that's not as critical a bug as not being able to create a rule at all