We had an issue on our System Variable (_PACKAGE_LAST_SUCCESSFUL_JOB_SUBMISSION_TIMESTAMP) which returns incorrect timestamp data for packages that ran between March 6th 1:43 PM UTC until March 7th 12 PM UTC.
What we know so far: Packages affected are recurring workflows which kickoff dataflows that anchor on the said variable (i.e. daily data load for instance which anchors on the workflow's last successful job timestamp).
This might cause data integrity issues for recurring data ingestion, etc. so please let us know if there's anything that we can do to help.
Please feel free to reach out if you have any questions or if think you were affected by the incident, and we will deduct the node hours accordingly at the end of the month.
We apologize for the inconvenience caused.
Posted Mar 07, 2019 - 17:23 IST
This incident affected: Infrastructure (Processing Engine).