Common Issues

This guide covers the most common problems you might run into while using Wayaframe and how to resolve them.

Project and sync issues

Project fails to load

If a project does not open or shows a loading error:

• Close the app completely and reopen it, then try loading the project again.
• Confirm you are signed in to the correct account.
• If the project is shared, confirm you still have access and check your internet connection.

Sync failures

Wayaframe syncs project data and assets in the background. If sync fails, you may see messages like:

• Asset sync failed or Asset sync incomplete: one or more media files failed to upload or download. Retry by reopening the project.
• Sync conflict: the project was modified on another device or by another team member while you were editing. Wayaframe will attempt to resolve conflicts automatically, but you may need to choose which version to keep.
• Remote updates detected: changes were made elsewhere since you last opened the project. The app will pull in the latest version.
• Project sync failed or Resync failed: the full project state could not be synced. Check your connection and retry.
• Remote project missing or Project not found: the project may have been deleted from another device or by another team member.
• Offline queued: changes are saved locally and will sync automatically when your connection is restored.

In most cases, syncing works reliably in the background and you never need to think about it. If you do run into a sync issue, try Resync from Cloud: click the project name in the editor header to open the project menu, then select Resync from Cloud. This forces a full resync of the project data from the server. See Project Sync for more details.

Media import problems

Import issues are usually caused by unsupported file types or download problems.

Unsupported files

Wayaframe supports most common media formats (see Import and Manage Media for details). If an import is rejected, check:

• The file type and extension are supported (MP4, MOV, PNG, JPG, WEBP, MP3, WAV, GIF, PDF, etc.).
• The file opens normally outside Wayaframe.
• The file is not corrupted or incomplete.

URL imports

When importing from a URL:

• The URL must be a direct http or https link to a media file.
• Some URLs may be region-restricted or require authentication, which will cause the download to fail.
• If a URL import fails, try downloading the file locally first and importing it from your computer.

Export problems

Export fails

When an export fails:

• Confirm the project is fully loaded before exporting.
• Retry the export after closing and reopening the project.
• Reduce the number of simultaneous heavy operations, especially on larger timelines.
• Check whether the problem happens on one project or across multiple projects. If only one project fails, the issue is likely project-specific.

Export warnings

Wayaframe checks your timeline before exporting and may show warnings for:

• Missing media: clips that reference files that could not be found. These clips will be skipped during export.
• Unsupported animations: some animation types may not render in the exported file.
• Animated GIF/WebP limits: animated GIF and WebP exports are limited to 15 seconds.

Warnings do not prevent the export from starting, but the affected clips may not appear in the final output.

Export takes too long

Export time depends on project length, resolution, number of tracks, and effects. For faster exports:

• Close other resource-heavy applications.
• Reduce the export resolution if a quick preview is all you need.
• Use the playback range to export only a section of the timeline instead of the full project.

Reporting export errors

When an export fails, a Report button appears on the error notification. Clicking it opens a feedback form with export context pre-filled, including the export format, resolution, clip counts, and platform information, so you do not need to type that out yourself.

For the fastest resolution, include your project file using the Attach Project File option in the form. This exports your full project so our team can open it and reproduce the exact failure. If your project contains sensitive content, remove it from the timeline before attaching.

Performance tips

If the editor feels slow or unstable:

• Close other heavy applications before working on large projects.
• Let background tasks (generation, sync, export) finish before starting another heavy workflow.
• Break unusually large projects into smaller sections when possible.
• If slowdowns are repeatable, report them through the feedback flow under the Performance or Crash & Stability category.

What to read next

• Recording Permissions
• Get Help