- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2021 12:20 AM
Hi Ryan,
Turns out post clone the Flow Engine Event Handlers had empty sysids. Their response 'This issue could be is related with Instance Clone is not clearing records from sys_properties and sys_trigger table as described in PRB1415852.
Deleting FEEH that has empty sys_id should be part of cleaning upon cloning to avoid this issue.' I can't locate the PRB though.
Wonder if a exclude/preserve could be made use of here but it's not a big fix anyway, once you know it. Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2021 05:20 AM
Ah, the instance I'm experiencing this in did just go through a clone recently... Thanks for the explanation!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2021 05:36 AM
This solved the problem, thank you so much!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2021 08:25 AM
I tried TJ's suggestions in my sandbox (which was cloned within a month ago) and my new flow went from way off schedule, to executing within 1 min of the displayed 'awake' time.
Many Thanks TJ for sharing your information!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2022 03:02 AM
you can try KB0967420 however deleting existing flow handlers seems to be drastic
