Schedule reporting error
A strange situation. A schedule report send almost 350 mails instead of 1.
Does anyone had similar situation?
also one DF to create a record created more records than expected.
I feel something wrong with 6.8 P2 scheduling!!
We had the same issue this past Sunday for our instance (6.7 p5) and we suspect that it is attributed to the time change since we are in a Daylight's saving timezone. We haven't been able to confirm this, so would be curious to hear if others have experienced this as well.
Experienced this as well in RSA hosted environment on 6.8 P1. A scheduled report distribution that sends a report to one user on the 1st of each month was sent 1,058 times.
Our "Notifications Sent" report shows no records with default filters (All Recipients, All Templates, Last 24 hours). If filtered by a user, notifications are displayed.
Opened case with RSA who replied indicating this is a known issue for all hosted customers and is being investigated. JIRA: Archer-100399
Yeah, I have also got the same updates from them.
It is not related to any specific version as we 3 are having same issue with different versions.
Hope they will have some solutions or workaround.
End users are not so happy getting 1000s of mail and 1000s of records.
For us it is impacted the Datafeed also.
I just wanted to confirm that Archer CE has been and continues to invest resources into isolating and resolving this issue. Yes, it have been an issue for weeks and we have been unable to root cause yet, but we are making progress.
I have a few questions for you:
- Is the situation isolated to monthly reported notifications or are other scheduled events impacted
- Impacting datafeeds: can you describe ?
- If monthly, did the problem occur in Sept?
- Do you see this in locations NOT impacted by US Daylight Savings on Sunday
If you have cases opened with CS please add this information there as well.
Are there specific scheduled report distributions that you know are impacted, and suggested workarounds for these (e.g. changing the date/time of delivery, or flat-out disabling them)?
Still currently investigating 11/1 SRD results but have already spotted troubling scenarios including VP-level being sent same SRD notification 1,829 times. Priority #1 is ensuring this does not happen again! Advice?
1. not only notification, datafeed also impacted
2. Dtafeed:- We had a scheduled data feed for month end last day to create some records, which ran on 25th of october instead of 31st of October. However we tried to change the date by disabling the DF and enabling it back but it wont scheduled for the correct day. We have created a RSA case for the same.
3.Did not notice it at that point in time. but today one user informed they have received more notification in last month than expected but not like this month. (we had an upgrade of 6.8 P2, only change )
we encountered same issue with campaigns, datafeeds and notifications. appears to impact anything that is scheduled (for monthly or quarterly only per rsa). same JIRA referenced. we are on 6.7P05 and it is impacting us as well. this is what RSA said....
Campaigns, datafeeds and notifications ran multiple times and I will be more than happy to assist with resolving your issue or answering any questions you may have. There is an open defect for this issue with Engineering under ARCHER-100399 - Monthly and quarterly Scheduled report distribution jobs are being sent repeatedly - There is nothing you can do to resolve the issue as it looks to be related to Archer's handling of Daylight savings time.
I recommend any you have setup on the next time change (Sunday, March 14, 2021) date to either be disabled if not required or moved to a different date (anything except for 14th or 7th (next time change is Nov 7th 2021)) to avoid this issue until it can be resolved as I expect it will be a code fix that will be required. (Unsure of how this will be delivered but, this looks to not just be isolated to you, in fact we just had many reported cases come in). Keep in mind this only looks to have effected jobs on a monthly/quarterly cadence.
We had the same issue yesterday with scheduled report distributions as well as a campaign job. It created multiple records. For now, we have inactivated the scheduled report distributions and created a support ticket. We are On-Premise. Interested in knowing how to ensure this does not happen again and if we need to watch out for other data feeds etc.?
Thank you for your responses. We are investigating the issue and believe that we have identified a way to reproduce the issue in our lab. I will let you know when we have root cause. Thanks gain !