ArticlesConsiderations for Upgrading Actuals to Spring 24

All versions 

Job Considerations When Upgrading to Spring 24

In Spring 24, a new job ‘ActualsCalculateDeltaContinuous’ for Actuals Calculation was introduced which processes Transaction Deltas in almost real time by using the queueable architecture. Read Continuous Calculation of Actuals to learn more about the job. On upgrade to Spring 24, this job is enabled by default. However, if there any issues, this job can either be paused or turned off for troubleshooting by setting the configuration options in Actuals Configuration Group as explained in the sections below. Note that these new configuration settings are not created automatically on upgrade. The Administrator must manually create them as needed. However, the system automatically sets the correct value for these settings in the backend (so not creating the configuration options does not result in any errors).

The scheduled ActualsCalculateDelta jobs are not removed after upgrading; it is optional to remove them manually. If the jobs are not removed, they are triggered every 15 minutes (as previously scheduled) but do not process any transaction deltas. Leaving the jobs makes sense if a user wants to disable the Continuous job and move back to a Scheduled job. If the scheduled jobs are removed, they must be recreated.

Pausing the Job

The preferred option is to continue using the Continuous job by pausing it for some time, reviewing and fixing the errors, and resuming the job. The steps to fix these errors are the same as before by going to the App Log and reviewing the errors that are created while processing Transaction Deltas. The main difference is the job will process the Transaction Deltas that errors more often than the Scheduled delta batch job which can result in more errors in the App Log. Fix these errors to avoid getting further app log errors for the same transaction deltas. An absence of any App Log errors means users will not encounter any issues.

How to Pause

This job can be paused by setting the config option AbortActualsCalculateDeltaContinuous job to true and can be resumed by setting the config option to false. On Upgrade, this config option must be created manually. 

Turning off the job

The other less preferred option is to turn off the job on upgrade. When the job is turned off, and if the user previously had the ActualsCalculateDeltaBatch job scheduled which was not manually deleted, the Delta job starts processing transaction deltas on the pre-existing configured schedule. If the Delta job was deleted manually, a new delta job must be created as documented in PSA: How to Schedule the Actuals Job to Run on a Particular Schedule.

How to Turn Off

This job can be turned off by setting the config option ‘UseActualsCalculateDeltaContinuous’ to false in the ‘Actuals’ Configuration Group. On upgrade, the config option must be created manually.

How to Create Configuration Options

On upgrade, use the following steps to create the configuration options AbortActualsCalculateDeltaContinuous and UseActualsCalculateDeltaContinuous:

1. Navigate to Configuration Groups
2. Click the Actuals Configuration Group
3. Navigate to the Related tab and click New
4. Add the exact configuration option name: AbortActualsCalculateDeltaContinuous and UseActualsCalculateDeltaContinuous
5. Select Type: Boolean
6. Add a version (e.g. 1)
7. Add any text in the description
   • Example for AbortActualsCalculateDeltaContinuous, set to true to immediately stop any continuous transaction delta processing. Set to false to allow the continuous transaction delta processing to resume
   • Example for UseActualsCalculateDeltaContinuous, given Calculation Mode is set to Scheduled; set to true to use continuous actuals calculations, set to false to use the batch job to calculate actuals

Continuous Job Specific App Log Errors

If there are app logs that contain the following error message, “A Job was enqueued but this execution context has no Queueables or Futures available”, this indicates that when a transaction delta was created there were no queueuables available to process it. The process automatically restarts when a queueable becomes available. So this app log can be deleted without taking any action. 

• Considerations for users upgrading to Spring 24
• Pausing the job
• Turning off the job
• Steps to create configuration options
• Continuous job specific App Log errors