Hi everyone,
I’m currently troubleshooting an issue where a Flow Designer flow appears to have become corrupted after syncing changes using the Now SDK workflow.
Context:
- The application is managed through VSF (Version Source File) and a local repository.
- I ran the Now SDK transform command to pull the latest changes from VSF into my local repo.
- After the transform, I redeployed the application back to my ServiceNow instance.
Issue:
After the deployment, the Flow Designer flow became corrupted. The flow does not behave as expected anymore and appears to have issues in its definition after the transform/deploy cycle.
What I’m trying to understand:
- Whether the Now SDK transform process can modify or incorrectly serialize Flow Designer metadata.
- If there are known issues with Flow Designer artifacts when moving between VSF and local repos.
- Whether flow actions, stages, or sys_ids can get affected during the transform.
Questions:
1. Has anyone experienced Flow Designer flows getting corrupted after using the Now SDK transform command?
2. Are there known limitations with Flow Designer artifacts when using source control / SDK workflows?
3. Are there recommended best practices to safely manage Flow Designer flows when syncing between VSF and a local repo?
Additional info (if helpful):
- The issue started immediately after the transform + redeploy.
- The flow worked correctly before running the transform command.
Any insights, debugging tips, or documentation references would be greatly appreciated.
Thanks in advance!
