Error message on our Scheduled PA job "'The job {0} is configured to be executed at {1} but the next scheduled execution on this group of indicators is at {2}" - Support and Troubleshooting

Error message on our Scheduled PA job "'The job {0} is configured to be executed at {1} but the next scheduled execution on this group of indicators is at {2}" Issue  Symptoms The error is being noticed in the UI for Time-Zone difference - stating that the indicators need to be run at different schedule than the users' profile.

It is being noticed at the release - MADRID

Release Madrid

Cause This Error Message is being triggered by the Business Rule that is being introduced at Madrid Release.

BR: Data collection job information

This BR is not existing at Kingston, London. It is existing at Madrid version.

Resolution This Error is caused by the function that is being called internally at the BR - getDisplayValueInternal()

This is due to a PRB - PRB1341509 .

GlideDate API Not functioning correctly: Not honoring getDisplayValueInternal() in Madrid .

This discrepancy has been observed at Madrid release.

Additional Information The PRB is Intended for a Fix at Later Releases.

However, as a Work-around (for temporary relief)

The user time/zone can be adjusted in-line with the Instance Time-Zone.

This is helping as a temporary workaround till the actual fix for the PRB is being rolled out.

For Example:

The instance "XXXXX" has been configured under timezone "Europe / Rome".

However, the timezone for the user is set to Europe/London.

Kindly configure the user profile to point to timezone = 'Europe/Rome'.