SAP Basis Tech Supports

Symptom
A job aborts with the error message “Cookie does not match”.
Other terms
Identity Center
Reason and Prerequisites
The defined timeout values is too short to allow the job to complete.
Solution
When the runtime engine starts processing an action task, it reserves the job in the Identity Center. While the job is running, the runtime engine will periodically update status information in the Identity Center. At this point, the Identity Center can return a status code to force the job to stop running. In this case the runtime engine will do a controlled exit.
The possible reasons for stopping the job are:
‘Job has been ordered to stop’
The user has pressed the “Stop now” button.’Not legal to mark running job in this state’
The job is not currently being allowed to run. It might be disabled, or more likely, marked as “Stopping”.’Cookie does not match. Please abort now!’
The job is not in the Identity Center’s list of running jobs.
The last reason usually appears when the job has ‘timed out’ The timeout is there to detect crashing jobs, network errors etc. If the timeout is set too short, the job can also time out when the job spends too much time processing an entry.
There are two timeouts for running jobs:
“Start timeout”"Execution timeout”
The values are configured on the “Options” tab of the Identity Center properties in the Management Console.
The “Start timeout” is the maximum time allowed from the job starts running, until it has processed the first entry.
The “Execution timeout” is the maximum time allowed between each time the runtime signals the Identity Center that it’s still active and running.
The last timeout value, the “Idle timeout” does not relate to running jobs, but must be high enough to handle the queue of jobs waiting to be processed.
Make sure that these timeout values are high enough for the jobs to be able to complete.
There is no performance impact on increasing these timeout values, but note that if for instance network problems prevent the jobs from running normally, it will take longer before a timeout error is detected and logged.