Integration Issues
Here are the common issues that arise when publishing to your Webflow site.
Conflict: The site hasn't been published
Publishing the articles will also publish the webflow site. If the webflow site hasn't been published before, then this error will follow.
Solution: Make sure that you publish your website at least once to every domain.
{
"message": "Conflict: The site hasn't been published",
"code": "conflict",
"externalReference": null,
"details": []
}
Conflict: Site is published to multiple domains at different times
Our integration effectively publishes the Webflow website, along with the collections. Strange enough, if you have multiple domains which are not synced, then this error will appear.
Solution: Make sure all domains are synced and published with the same version.
{
"message": "Conflict: Site is published to multiple domains at different times",
"code": "conflict",
"externalReference": null,
"details": []
}
Conflict: The collection structure changed since the last publish
If you've changed your collection after setting up the integration, it's possible that the fields have changed and we're not able to map them accordingly.
Solution: Review your integration to make sure the fields are properly mapped. If that still doesn't work, try deleting your integration and creating a new one. After checking it, please make sure you republish your Webflow website to all domains.
{
"message": "Conflict: The collection structure changed since the last publish",
"code": "conflict",
"externalReference": null,
"details": []
}
Request not authorized
If the API token you inserted (if you did this manually), does not have the necessary scopes, then publications might also fail
Solution: Make sure your API token has all the permissions required. Re-authenticate to make sure.
{
"message": "Request not authorized",
"code": "not_authorized",
"externalReference": null,
"details": []
}
Validation Error
In the integration settings, you map certain values to your collection's columns. If the collection has more fields and they're marked as required, then publications will fail. Moreover, if some fields have extra validations (for example maximum length), then the publication might fail.
Solution: Mark these fields as not-required in your collection settings on Webflow.
{
"message": "Validation Error",
"code": "validation_error",
"externalReference": null,
"details": [
{
"param": "post-excerpt",
"description": "Field is required: null"
}
]
}
Updated 17 days ago