Your flow cannot be found. Flow sys_id:p definition - Actions not available from update set.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2023 09:12 AM
I have several actions that make REST calls to our vendor. Everything works as expected in DEV. When the flows/actions were pushed to our other environments via and update set, they will not open and show the following:
Content not found
Your flow cannot be found. Flow sys_id:p definition
These are copies of DEV connections with updated parameters for prod. All of which, both the original and the copy, work as expected in our dev environment.
Has anyone else experienced this, or a similar issue?
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2023 04:26 PM
Were the trigger conditions changed? I have had similar issues updating the trigger, where we disabled the current prod ones, and added new ones.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2023 12:27 PM
Sorry for the delay in responding. It turns out there was a plugin used in one of my actions that had not been propagated to our production environment.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2024 05:21 PM
This is a good tip Victor. This is the only thread on google that shows the exact error message I was getting and it was because the Integration Hub plugin wasn't active in the target instance. I encountered this when restoring a Scoped App from a Source control repository.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2024 09:41 PM
Yep, in my case it was on a PDI, and the Payload Builder action was not installed. As soon as I installed it, the flow was able to load!
