ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Daylight Saving Change Causes RAJ Flow to Stop Synching

book

Article ID: 238275

calendar_today

Updated On:

Products

CA Agile Central SaaS (Rally) CA Agile Central On Premise (Rally)

Issue/Introduction

When looking at the Last Run date for a flow it is noticed that the date hasn't incremented.  The date listed in the Last Run field coincides with a time change due to daylight saving.

 

Viewing the tomcat-logs on the adapter container reveals an error as follows:

2022-03-29 14:07:45,224 ERROR r.T700769 [http-nio-8080-exec-23219] [Jira API][_fetchUpdates] Error response from Jira GET requestjava.lang.RuntimeException: java.lang.Exception: {"errorMessages":["Date value '2022/03/13 02:00' for field 'updated' is invalid. Valid formats include: 'yyyy/MM/dd HH:mm', 'yyyy-MM-dd HH:mm', 'yyyy/MM/dd', 'yyyy-MM-dd', or a period format e.g. '-5d', '4w 2d'."],"errors":{}}

 

Environment

Release : 3.4.1

Component : Rally Adapter for Jira

Resolution

Workaround:

To resolve this:

  1. Set the stopProcessing flag to 1
  2. Edit the Last Run for the flow and set it back two minutes
  3. Set the stopProcessing flag to 0

 

Resolution:

This issue is resolved in RAJ 3.5

 

Attachments