- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2022 06:04 AM
Hello all 🙂
We're having an issue with RITMs not recieving a workflow upon creation. They're created by an external system through the regular table API.
RITMs are create correctly, but their workflow only trigger ever so often, the rest will just have the "start workflow" option on the record. Its not cancelled or similar, its simply not started from what I can tell; context is empty on these records.
Seems to happen at random, same order type, same catalog item, same workflow etc. - but this time it won't work.
Anyone had experience with this issue? Its kinda headscratching to be honest 😄
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2022 11:49 PM
Found out it was a BR that starts the workflow once inserted via the API. Was only set to trigger on update, which was the issue.
Thanks for the feetback though 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2022 06:34 AM
Hmm, It does generate an error while using the "tryit" functionallity.
Unique Key violation detected by database ((conn=59360) Duplicate entry '789648dd1b75d110b1afea41604bcba8' for key 'PRIMARY')
That sysid is the Request.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2022 11:49 PM
Found out it was a BR that starts the workflow once inserted via the API. Was only set to trigger on update, which was the issue.
Thanks for the feetback though 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2023 05:30 AM
Hi ,
Can you please share the BR name , in case its OOB , we are facing a similar issue.