Recurring Record Templates - New Releases, Update to Recurring Rules, Running in 25.2

No-Code Platform
1

I have a few questions on recurring record templates for an application.

  1. Is it expected that with a new release we have to go back in and update all job schedules with the new environment? With the recent move to 25.2, when I went to do a manual run from Job Scheduler to test the job, I received an error due to environment. The job scheduler still had 25.1 as the environment.

  2. I edited the recurrence of this same job from the application Edit Recurrence Rules screen and changed the ending date from 9/1/2030 to 9/1/2028. The job scheduler was not updated to reflect this new end date. I assume this is a bug in 25.2?

  3. I modified the job schedule to run in my LC after updating environment. I am now getting a Nate error. And when I look at the details it doesn’t seem to know the name of the record template. The nwid is the same as it was in 25.1.

    image
    image1920Ă—1032 126 KB

    image
    image1920Ă—1032 116 KB

    So, in general are there actions for us to do on recurring record templates and their job schedules when we upgrade to a new release?

2

Hi @mhylton,

  1. Yes - you will need to maintain your recurring templates at release upgrade boundaries. We do not currently do that automatically on behalf of the user.
  2. I would agree with you that this is a bug. Please work with your team to get a ticket or bug filed with the Platform team with reproducible steps.
  3. Can you tell me more about this use case? Did you create your template in lifecycle A and then updated the Job Scheduler to run in lifecycle B?
2 Likes
3

Cheyanne,

Case #3. Template came over from 25.1 where it was created in the the same LC we are using in 25.2. Though when it created it, the scheduler was created with LC on the schedule is set to base. I reported a bug in 25.1 (BOT-37900 in backlog) that doesn’t allow you to run a recurring template in your LC from the application Run Now option. Therefore as a work around here is what I was given to test the job scheduler in my LC.

  1. Open Job Scheduler application, and search for the job.

  2. Inactivate the job, then deselect “Run in Default Lifecycle”.

  3. Update the job to your lifecycle. Then activate.

I just went back to the app template management, it was there earlier but looks like its been deleted, so I set up a brand new one. I am able to run without the Nate error but one of the fields I am populating and is required is not passing through, and therefore throwing an error. So I will add this to the bug I am creating.

Thanks for your help.

1 Like
4

Thank you for the additional details, @mhylton. I tried recreating your bug in with my own application and wasn’t able to reproduce. Templates are not metadata, they’re not lifecycle aware. It should not matter what lifecycle you run your job scheduler in so I have a feeling it has to do with the release upgrade boundary rather than running in one lifecycle or another. I will keep an eye out for the bug and add some comments for whoever picks it up from the backlog.

2 Likes