Troubleshooting

Solutions for problems that come up when generating, syncing or running Portman collections.

Redirect tests pass in Newman but fail in Postman

Newman is set to ignore redirects so redirect response codes can be tested. In the Postman app, turn off Postman, Preferences, Automatically follow redirects, or your redirect tests will fail.

Schema validation fails on unknown formats

If your schemas use formats the JSON schema validator does not know, add them with --extraUnknownFormats:

portman -l ./tmp/specs/crm.yml -o ./tmp/specs/crm.postman.json --extraUnknownFormats ulid one two

This makes schema validation more lenient for those formats.

Schema validation fails on extra properties

If you enabled "additionalProperties": false on schemaValidation, any undocumented property in the response fails the test. Document the property in your spec or remove the option. See Contract tests.

Conversion fails on circular references

Pass --ignoreCircularRefs to ignore circular references in the OpenAPI spec.

Warnings about missing operationIds

Portman warns when targets reference operationIds it cannot find. Check the IDs in your config against the spec, or switch to openApiOperation targets. To silence the warnings, use --no-warn.

Postman sync is slow or returns 5xx errors

For large collections, the Postman API compares all requests during an update. Use --postmanFastSync to delete and recreate the collection instead. This gives the collection a new UID on every sync.

Postman sync uses stale data

Portman caches Postman API data in .portman.cache.json. Delete the file or pass --postmanRefreshCache.

Custom Postman config stopped working after upgrading

Since version 1.28.0, a custom openapi-to-postman config passed with --postmanConfigFile must set parametersResolution to "Example" or "Schema". The options requestParametersResolution and exampleParametersResolution are deprecated.

Chained requests use the wrong ID

Requests run in collection order. Make sure the request that assigns the variable runs first, using orderOfOperations or orderOfFolders in globals. Check the variable name Portman logs for each assignment; variableCasing changes generated names.

Too much console output from assigned variables

Turn off the logging with --logAssignVariables false.