Skip to content


Smartconnect RunNumber in Process Errors does not match the actual run number

Alyson Van Alstyne asked 7 years ago
During test upgrade, RunNumber and Process errors matched, but after live upgrade, the RunNumber for the map doesn’t match…Map actual run  is 2, the process error window shows run 4, so there is no data to fix in process errors.
This is for existing and new maps….
Patrick Roth Staff answered 7 years ago
This is a known issue that we’ve seen in SmartConnect a few times.  We’ve been unable to repro this on demand in-house so it is likely an issue with inconsistent data somehow in the SC database and/or a bug.
We are working with the customer on this case current and with development on the issue.

If you would like to submit an answer or comment, please sign in to the eOne portal.