📋 System Logs

AssetFlow’s Logs page provides a real-time terminal view of all engine events, upload progress, and debug information. It’s your window into what the application is doing at any moment.

Log Types

Logs are color-coded by type for quick scanning:

Filtering Logs

Each log type has a toggle checkbox at the top of the logs page. Uncheck a type to hide its messages from the view. By default, all types are shown.

This is useful when you want to focus on errors only or monitor successful uploads without noise.

Exporting Logs

Click the 📤 Export Logs button to save the current log buffer to a text file. The exported file includes:

• Timestamp for each entry
• Log type (Info / Success / Error / Warning)
• The full message text

Exporting is useful for:

• Debugging — Share logs with support on Discord
• Record keeping — Save a session’s activity for later review
• Bug reports — Attach relevant log sections when reporting issues

Common Log Messages

Log Guide

This guide explains every log message and error that can appear in AssetFlow’s Logs panel during a reupload or while saving settings. All logs are displayed in English regardless of your interface language, so you can match them directly from a ticket or support session.

Pre-Start Errors

These errors block the reupload before it begins. A “Reupload blocked” popup appears and nothing is uploaded.

Moderated Account (Cookie or API Key)

Log message:

[Moderation] ⛔ Cookie account "XXX" — account has been terminated / restricted / banned / moderated (economy access blocked).
[Moderation] Asset downloads will fail while the account is moderated.
[Moderation] Switch to an unmoderated cookie account and try again.

(or the same with API key owner instead of Cookie account)

What it means: The Roblox account used (cookie or API key owner) has been banned, restricted, or moderated by Roblox. AssetFlow detects this before starting and blocks the reupload to avoid wasted attempts.

Solution: This cannot be fixed from within AssetFlow — it is a Roblox-side account penalty. You must either:

• Switch to a different, unmoderated Roblox account, or
• Wait for the restriction to lift if it is temporary.

Unpublished Game (placeId = 0)

Log message:

PlaceId = 0 — publish your game first! The plugin must be connected to a published place.

What it means: The Roblox Studio plugin is connected to a place that has never been published. AssetFlow cannot link assets to an unpublished place.

Solution:

• Publish the game at least once via File → Publish to Roblox in Roblox Studio, then try again.
• Alternatively, use the file mode (.rbxl) which does not require a published place.

Missing API Key

Log message:

API Key missing! Configure your Open Cloud API Key in Account settings.

What it means: No Open Cloud API key is configured on the active account. AssetFlow requires a key to upload assets.

Solution: Go to Account → Open Cloud API Key, create a key at create.roblox.com  with the scopes asset:read, asset:write, and asset-permissions:write, then add it in AssetFlow.

API Key with Missing Permissions (Blocking)

Log message:

🔑 API Key configuration problem:
<list of missing permissions or non-whitelisted IP>
➡ Fix this on create.roblox.com > Credentials > your API key.

What it means: At least one of the three required scopes is missing (asset:read, asset:write, or asset-permissions:write), or the client’s IP address is not authorized on the key. AssetFlow blocks the reupload entirely to prevent silent failures later.

Solution: Go to create.roblox.com → Credentials → your API key and:

• Confirm all three scopes are checked.
• Confirm 0.0.0.0/0 is in the allowed IPs (unless you intentionally restricted it — in that case, add your current IP).

Once corrected, relaunch the reupload. The key will be revalidated automatically before it starts.

API Key Warning (Non-Blocking)

Log message:

⚠️ API Key: <detail>
The upload will continue but permissions won't be able to be granted.

What it means: A minor issue was detected during key validation (for example, an IP restriction that prevents verifying one permission), but the three main scopes responded OK. The upload continues, though “give access” permission grants may not work.

Solution: No immediate action is required. If you want to ensure permission grants work correctly, verify your scopes and IP allowlist as described above.

Not Friends on Roblox (User Permission Mode)

Log message:

❌ Permission not possible — user <ID> is not your friend on Roblox.
Add them as a friend and try again.

What it means: Access was configured for a Roblox user ID that is not in the account’s friends list. Roblox requires friendship to share asset access with another individual user.

Solution: Add the target user as a friend on Roblox, then relaunch the reupload. (If you accidentally entered your own user ID, that case is handled automatically — you do not need to be friends with yourself.)

Not a Member of the Group (Permission or Destination)

Log message:

❌ Permission not possible — you are not a member of group <ID>.
Join the group and try again.

or

❌ Reupload not possible — you are not a member of group <ID>.
Join the group and try again.

What it means: The account is not a member of the target group — either the group you are trying to grant access to, or the group you selected as the upload destination.

Solution: Join the relevant Roblox group, then relaunch the reupload.

Insufficient Role in Group

Log message:

❌ Permission not possible — your role in group <ID> does not allow managing assets.
Ask the group owner to grant you "Manage Group Assets" rights.

or (direct upload variant)

❌ Reupload not possible — your role in group <ID> does not allow uploading assets.
Ask the group owner to grant you "Manage Group Assets" rights.

What it means: The account is a member of the group but its role does not have the Manage Group Assets permission enabled.

Solution: Ask the group owner or an admin to enable Manage Group Assets for your role in the group settings on Roblox.

Per-Asset Errors

These errors appear one by one for individual assets and do not stop the rest of the batch from processing.

Invalid or Expired API Key

Log message:

[ID] Invalid or expired API Key

What it means: The API key has been deleted, regenerated, or has expired on Roblox’s side since it was saved in AssetFlow.

Solution: Regenerate or verify the key at create.roblox.com , update it in AssetFlow, then relaunch.

Roblox Rate Limit

Log message:

[ID] Error (attempt X/3): Open Cloud rate limit — wait a moment and retry

What it means: Too many requests were sent to the Roblox API in a short period of time and Roblox is throttling them.

Solution: No action needed — AssetFlow retries automatically (up to 3 attempts with increasing delays). If many assets still fail after all 3 attempts, wait a few minutes then relaunch using only the failed assets.

Roblox Audio Upload Quota Reached

Log message:

[Audio Quota] ⛔ Roblox audio upload quota reached.
[Audio Quota] Your Roblox account has hit its daily/monthly audio upload limit.
[Audio Quota] This is a Roblox-side restriction — not an AssetFlow issue.
[Audio Quota] → Try again tomorrow, or upgrade your Roblox account.

What it means: Roblox limits the number of audio files a given account can upload per day or per month depending on the account tier (free vs. Premium/paid). AssetFlow stops processing remaining audio assets immediately once this is detected to avoid wasting attempts.

Solution: This cannot be fixed from within AssetFlow — it is a Roblox-imposed limit. Options:

• Wait until the next day (daily quota) or the next billing period (monthly quota).
• Upgrade to a higher Roblox account tier with a larger audio quota.

Content Moderated by Roblox (400 + Auto-retry)

What it means: Roblox rejected the upload because the asset name triggered its moderation filter. AssetFlow automatically retries with the name [Censored] — this is silent and you will see no error if the retry succeeds.

Log message (if the retry also fails):

[ID] Error (attempt X/3): Upload 400: <Roblox message>

Solution: Check the exact Roblox message in the log. If it indicates a content issue (not just the name), the file itself may be refused by Roblox moderation. There is no guaranteed fix from within AssetFlow — try renaming or slightly modifying the asset before reuploading it.

403 Forbidden from Roblox

Log message:

[ID] Error (attempt X/3): 403 Roblox: <reason>

What it means: Roblox refused the upload due to a permissions issue — usually related to the API key scopes or the account’s rights on the target group.

Solution:

• Verify the API key scopes (asset:read, asset:write, asset-permissions:write).
• If uploading to a group, verify the account’s role has Manage Group Assets rights.

Source Asset Download Failed

Log message:

[ID] Access denied. Asset may be private or deleted.

What it means: AssetFlow could not retrieve the original asset from any source (primary, friends fallback, or semi-private fallback). This typically means the asset was deleted by its original creator, or its sharing permissions are too restrictive.

Solution:

• Open roblox.com/library/<ID> to check if the asset still exists. If it returns a 404, it has been deleted and cannot be recovered.
• If the asset exists but is private, only its original creator can change its sharing settings on Roblox. AssetFlow cannot bypass this.

Generic Failure After 3 Attempts

Log message:

[ID] Failed after 3 attempts: <exact error message>

What it means: This is a catch-all entry. The specific cause is identified by the exact message that follows. Read the rest of the log line and match it to the relevant entry above.

Solution: Refer to the specific error message shown in the log. If the message does not match any entry in this guide, share it in the AssetFlow Discord  support channel so it can be added.

Save Errors

These errors occur when saving account settings, outside of an active reupload.

API Key Save Failed (Missing Permissions)

What it means: A “Missing API Permissions” popup appears and the key is not saved. The same scope or IP issues described in the pre-start section were detected at save time — AssetFlow validates the key immediately when you save it, not only at reupload time.

Solution: Same as the API Key with Missing Permissions entry above — fix the scopes and IP allowlist on create.roblox.com , then save the key again.

Network Unreachable During Verification

Log / UI message:

Network unreachable — could not verify API key.

What it means: AssetFlow could not reach Roblox’s servers to verify the API key. This is caused by the client’s internet connection being down or unstable, or by a global Roblox outage.

Solution:

• Check the client’s internet connection.
• If Roblox is experiencing a global outage, wait for it to resolve (check status.roblox.com ).

File Save Failed (.rbxl)

Log message:

Failed to save file.

(or a more specific system error message)

What it means: AssetFlow could not write the .rbxl file to disk. This is caused by a full disk, insufficient write permissions on the destination folder, or an invalid file path.

Solution:

• Check that the destination drive has enough free space.
• Verify that the account running AssetFlow has write permissions on the selected destination folder.

Quick Reference