Problem Description
When pmcmd StartWorkflow command is run after importing and replacing workflows into existing repository folders, the following error appears:
“Error: Folder [ID=xx] not found”.
Cause
The error occurs because of repository agent connection caching. Upon running a workflow, the Integration Service caches the folder ID, workflow and other metadata information so that subsequent runs start fast as time taken for metadata fetch would be lesser. If the said workflow is replaced, it gets saved with a new workflow ID tied to folder ID. When the workflow is started using pmcmd, the saved metadata is reused as the workflow name is same but leading to a different workflow ID, thus leading to the error.
This error can also occur if the folder of the workflow was renamed and a new folder with the original name was created.
Solution
This is a known issue and a Change Request (CR 223242) has been submitted to be addressed in a future release.
Workaround
To resolve this issue, use one of the following workarounds:
More Information
Note
Alternatively, disabling repository agent caching option should serve as another possible workaround. Should you wish to adopt this workaround
When pmcmd StartWorkflow command is run after importing and replacing workflows into existing repository folders, the following error appears:
“Error: Folder [ID=xx] not found”.
Cause
The error occurs because of repository agent connection caching. Upon running a workflow, the Integration Service caches the folder ID, workflow and other metadata information so that subsequent runs start fast as time taken for metadata fetch would be lesser. If the said workflow is replaced, it gets saved with a new workflow ID tied to folder ID. When the workflow is started using pmcmd, the saved metadata is reused as the workflow name is same but leading to a different workflow ID, thus leading to the error.
This error can also occur if the folder of the workflow was renamed and a new folder with the original name was created.
Solution
This is a known issue and a Change Request (CR 223242) has been submitted to be addressed in a future release.
Workaround
To resolve this issue, use one of the following workarounds:
- Specify the folder name to the pmcmd startworkflow command using –f switch. –f is not mandatory but helps in this case to avoid the error.
- If the -f option is already used, check if the workflow name is unique and try without the -f option.
- Restart the Integration service. Restarting the Integration Service releases the cached metadata.
- Import the workflows into a new folder and start the workflow from that folder.
More Information
Note
Alternatively, disabling repository agent caching option should serve as another possible workaround. Should you wish to adopt this workaround
No comments:
Post a Comment