Issue Management Workflow not working
Summary: user_55d43f is experiencing an issue with a Collibra workflow. The workflow, meant to trigger when report assets are added, only functions correctly when assets are manually added. However, when a homegrown application adds reports weekly, the workflow does not trigger, and there are no errors or indications in the Collibra console logs. user_55d43f is seeking advice on whether others have encountered similar issues and how they resolved them, suspecting a possible lock by Collibra during the application run.
Hello,
We are currently using the issue management workflow Collibra provides. The workflow should be triggered when there is a report asset added to Collibra. The workflow works when we manually add report assets. However we have a weekly homegrown application that adds reports, when the application runs unfortunately the workflow is not triggered. According to the logs from the Collibra console, there are no errors but also no sign the workflow is being kicked-off. I wasn't sure if Collibra turns on a lock or something similar when the program runs to ingest the new report assets that would prevent the issue management workflow from starting.
Has anyone ran into a similar issue and if so how did you resolve it?
Thanks for the help!
George Cheung
·7 months agoHi, it sounds like you have the issue management workflow set up to with a start event of 'Asset Added' - this is why it works when done manually, while the homegrown application sounds like it is utilizing the import api.
The following page details that the start events were not meant to be used in conjunction with the import api:
https://productresources.collibra.com/docs/collibra/latest/Content/Workflows/ManageWorkflows/co_general-wf-settings.htm
What you can do is have a workflow that runs and finds the newly created assets (from the recent import) and starts the issue management workflow on those assets, this additional scanning workflow can be triggered at the end of the homegrown application, or its contents can be programmed into the homegrown application itself as there are rest and java api (workflow) to scan for new assets and to start workflows.
Hope this helps.