| | |
Table deleted. Please reconfigure the workflow. | The table has been deleted. | Reconfigure the automated workflows and select another table. |
Record to be updated did not exist | Only appears for "Edit Record" when the target record to be edited does not exist. | Reconfigure the automated workflows. |
Field deleted. Please reconfigure the workflow. | The field has been deleted. | Reconfigure the automated workflows and select another field. |
Record limit in the table reached. Unable to add more records | The table has reached the row limit. | Reconfigure the automated workflows and select another table. |
The user who activated this workflow was not in the selected group. | The user is not in the target group, so the message cannot be sent. | Join the group to which the message is directed or change the group. |
The workflow was turned off during the execution process. | The workflow configurator has closed the workflow, causing the workflow to terminate. | Restart the automated workflows as needed. |
Maximum number of message recipients reached. Please try using Base Assistant to send messages. | When sending automated messages as an individual user, the number of chats should not exceed 20, and the number of groups should not exceed 5. | Use "Base Assistant" to send automated messages |
| The maximum response duration is 20 seconds. If no response is received after 20 seconds, it will time out. | - If the base does not need to obtain the request result, there is no need to troubleshoot this error. You can confirm the final request result with the party being called.
- If the base needs to obtain the request result, you need to adjust the execution settings of the party being called to return the result before the timeout.
|
The returned data format is incorrect. Please check if it conforms to the response format. | The content returned by the HTTP request may include the default values of request headers (such as content-type), resulting in failure to recognize the data format. | Check and delete the default values of the request headers and then try again. |
The URL is blocked. Please check your WAN connection. | HTTP requests do not support intranet URLs. | Replace the request URL. |
This attachment field can only be filled via mobile. Please reconfigure the action. | "Only allow photos/videos taken in real time via mobile devices" is selected for the attachment field used in the automated workflow. This setting cannot be changed through the automated workflow. | Check the settings of the attachment field (deselect "Only allow photos/videos taken in real time via mobile devices"), or select other fields. |
This location field can only be filled via mobile. Please reconfigure the action. | "Allow real-time mobile locating only" is selected for the location field used in the automated workflow. This setting cannot be changed through the automated workflow. | Check the settings of the location field (deselect "Allow real-time mobile locating only"), or select other fields. |
Unable to message external users via Base app. Please send messages by Base assistant or as a user if needed. | Base apps cannot send messages to external users or groups. | Change the identity of the sender to "Base Assistant" or your own identity. Using your own identity, you can send messages to external contacts or external groups you belong to, but not external users who are not your contacts. The Base Assistant has no restrictions. |
| It is possible that the message recipients include external users who are not contacts (users who have not been added as a contact). This error may occur when you use Base app or your own identity to send automated messages. | Try changing the sender identity to "Base Assistant". |
| @mention all is not supported in the message card. | |
Total number of pictures exceeds 100 limit. | You can add at most 100 images at a time to a message card. | Reduce the number of images. |
The size of pictures exceeds 10 MB limit. | Only images 10 MB or smaller are supported. | |
Attachment format not supported. | You can only insert images in a message card, and the supported image formats include JPEG, PNG, WEBP, GIF, TIFF, BMP, and ICO. | Delete non-image attachments (such as videos and PDF files). |
| You've added an image in an unsupported format, or the image contains non-compliant content. | Change the image. The supported image formats are JPEG, PNG, WEBP, GIF, TIFF, BMP, and ICO. |
The size of message content exceeds 30 KB limit | | |
Your organization has reached the maximum number of times that automated workflow can be used. | | Contact Support to upgrade to a different plan or rerun the workflow the next month. |
Workflow is in infinite loop. | The actions in the workflow will continuously trigger new actions, causing an infinite loop. For example, both the trigger and actions are to add a record, and the same table is selected. | Modify the workflow configurations. |
Triggers limited within a short period of time | Automated workflows can be triggered up to 10,000 times per minute. | Check the edit history to see if a collaborator copied and pasted a large amount of data. Then wait a while before running the workflow again. |
Dashboard loading timeout | Too much dashboard content. | Reduce the amount of content in the dashboard and retry. |
Dashboard size exceeds limit. Consider reducing the number of charts and try again. | The height of the dashboard exceeds 100 grids. | Adjust the height or number of charts in the dashboard. |
An internal system error occurred. | An error occurred in automation or messaging system. | Retry the process later, or contact Support for technical help. |
The field type doesn't match. | It may be because a redirect link has been configured in the automated workflow, but the address of the redirect link is not a URL. For example, when you reference a hyperlink field, you must select Link address, and not directly reference the hyperlink field. If the field type for the field referenced in the automated workflow has been changed, then this error may also occur. | Check the referenced field type and settings, modify the automated workflow, and try again. |
AI rate limit reached for requests. Please try again 1 hour later. | Automated AI calls reached the rate limit (can call up to 1,800 times per hour). | |
Bots can't send messages. The group turned on "Only group owner or group administrators can send messages". | Message-sending permission is turned on for the recipient group, and Base Assistant isn't the group owner or a group administrator. | Turn on "All group members can send messages." |
Unable to add bots. The group turned on "Only group owner and group admin can add members or share group". | Member-adding permission is turned on for the message recipient group, and the person configuring the workflow does not have permission to add Base Assistant to the group. | Request a group administrator to add Base Assistant to the group. |
Bot not in the selected group. Please add the bot to the group and try again. | The bot you selected is not in the group, so it cannot send automated messages. Note: When you use Base Assistant to send automated messages to an external group, but the group already has a Base Assistant that was invited into the group by external users, then your Base Assistant can't be invited into the group. | You can switch to another identity to send messages, or remove the existing Base Assistant. For example, if you want to sending messages to external groups, you can use your own identity to send automated messages, as long as you're in the group. |
Unable to activate this workflow. Recipient configuration error. | The recipient does not exist, or the user account status is abnormal. | Reconfigure the recipient. |
Editors' permissions of this workflow have been changed. | The person configuring the workflow no longer has permission to edit or modify the workflow. | Re-create the workflow or change the permission for the editor. |
The editor has left the organization. | | The Base owner needs to reactivate the automated workflow. |
This workflow does not exist/has been deleted. | Someone else has deleted the workflow. | |
Records have been deleted. | The records used in the workflow have been deleted. | Modify the workflow configurations. |
Workflow has been blocklisted. | The workflow contains non-compliant content. | Modify the workflow configurations or contact Support. |
Maximum number of reruns has been reached | | Modify the workflow configurations, then try again. |
Workflow exceeded maximum time allowance to rerun. | Currently, workflows can rerun for a maximum of 2 hours. | |
Workflow exceeded maximum run time. Running result might be affected by the actual situation. | The time used to run the workflow has exceeded the limit. | Check the final run results in the activity log. |
The interval between two reruns is less than the minimum time requirement. Please try again after 1 minute. | | Wait for a while, then try running the workflow again. |
Workflow has been updated and can't be rerun. | The configurations for the workflow have been changed. | Create a new automated workflow with the same configurations as before. |
