FramerGo - Known Issues & Limitations

Last updated: March 2026

Framer API Limitations

  1. Publish timeout on large sites

Framer's publish and deploy process can take a long time for sites with many pages or large assets. FramerGo enforces a 90-second timeout on publish operations. If your site consistently takes longer than this to publish, the job may be marked as failed even though the CMS content change was applied successfully. In this case, the content update still goes through — only the automatic publish step is affected.

Workaround:

For very large sites, schedule a separate Publish Site job a few minutes after your CMS update to give Framer more time.

  1. Draft status updates may require a retry

In some cases, Framer's API may silently fail to update an item's draft status on the first attempt. FramerGo detects this and automatically retries using an alternative method, then verifies the change was applied. This is handled transparently — no action needed on your part — but you may occasionally see an extra log entry in the Execution History showing the verification step.

  1. Reserved domain errors during deploy

Certain Framer domain configurations (particularly default framer.app or framer.website domains) can cause a "reserved domain" error during the deploy step. FramerGo automatically falls back to deploying without those hostnames, ensuring your site still gets published to your custom domain. ---

Platform Limitations

  1. Maximum 5 concurrent jobs

FramerGo processes up to 5 jobs at the same time. If more than 5 jobs are scheduled for the exact same moment, additional jobs are placed in a queue and executed as soon as a slot becomes available. In practice, this delay is typically just a few seconds.

  1. CMS text field length

Text content sent to CMS fields is limited to 500 characters and HTML tags are stripped. If you need to publish longer-form content, consider updating the content directly in Framer and using FramerGo to handle the publish/deploy scheduling.

  1. Brief recovery window after server maintenance

During scheduled maintenance or server restarts, there may be a delay of up to 5 minutes before pending jobs are re-initialized. A background watchdog process automatically recovers any jobs that were waiting to fire during this window. No jobs are lost — they may just execute a few minutes later than originally scheduled in rare cases.

  1. Duplicate CMS item prevention

When creating CMS items, FramerGo checks for existing items with the same slug to prevent duplicates. If a matching slug already exists, the creation is skipped and the existing item is used instead. This is by design to prevent accidental duplicate entries, but it means you cannot create two items with identical slugs. ---

Reporting Issues

If you encounter an issue not listed here, please reach out to us at support@framergo.com. Include the job ID from your Execution History and we'll investigate promptly.