When a contact is triggered to enroll in a flow but fails to proceed, it’s usually due to missing information, permission issues, or system limitations.
This article explains the common flow enrollment errors you may see in Advanced Flow Builder, what each error means, and how to resolve it so your workflow can run smoothly.
⚠️ If an error continues after applying the steps suggested, contact our support team and include the Remarks error for faster troubleshooting.
💡 Flow enrollment errors are shown in Remarks with further explanation given in Flow logs to help identify why a specific contact or action couldn’t continue in the workflow.
Below are the details for each error:
Invalid or missing information
| Remarks error | What it means | Possible solution |
| Phone number format is invalid | The phone number doesn’t follow the required format or is missing a country code. | Ensure the phone number includes a country code (for example, +1 555 123 4567). |
| Email address format is invalid | The email address format isn’t valid. | Ensure the email address is in a valid format (for example, name@example.com) |
| Missing required value | A required field is empty or missing. | Ensure the required field contains a value before continuing. |
| Missing phone number or email address | The contact doesn’t have a phone number or email address to identify them. | Ensure the contact has a phone number or email address |
| Field format is invalid | The value entered doesn’t match the required format. | Ensure the value match the expected format |
| Field value cannot be processed | The value type doesn’t match what the system expects (for example, text instead of number). | Ensure the field using the correct data type |
| Date/time format is invalid | The date format isn’t supported | Ensure the date/time uses a supported format (for example, YYYY-MM-DD or MM/DD/YYYY). |
| Unsupported media type | The file type or size isn’t supported by the selected channel. | Ensure the file type and size are supported by the selected channel |
| Missing phone number | The contact doesn’t have a phone number required for the action. | Ensure the contact has a valid phone number |
| Format is invalid | The variable expression contains invalid syntax or unsupported operators. | Ensure the variable expression is written in a supported format |
Referenced data not found
| Remarks error | What it means | Possible solution |
| Contact not found | The contact no longer exists or has been deleted. | |
| Team member not found | The assigned team member is inactive or deleted. | |
| Team not found | The selected team has been deleted or deactivated. | |
| Channel not found | The messaging channel is disconnected or removed. | Ensure the messaging channel is still connected in Channel settings. |
| Conversation not found | The conversation thread no longer exists. | Ensure a conversation exists for this contact on the selected channel |
| Ticket type not found | The ticket category or template has been deleted. | |
| Custom object record not found | The referenced custom object record no longer exists. | |
| External record not found | The record doesn’t exist in the connected external system or lack of related permission access. | Ensure the external record exists and the integration has permission to access it. |
| AI agent not found | The AI agent has been deleted or reset. | Ensure the AI agent is still set up and available in AI settings. |
| Recipient not found | The contact doesn’t have an existing conversation on this channel (for example, Facebook or Instagram). | Ensure the contact has an existing conversation on that channel |
Flow rules reached
| Remarks error | What it means | Possible solution |
| Phone number already exists | The phone number is already used by another contact. | |
| Email address already exists | The email address is already associated with another contact. | |
| Record already exists | A unique field value already exists. | |
| Contact already enrolled | The contact has already entered this flow and multiple enrollments aren’t allowed. | Ensure the flow’s enrollment settings allow re-entry if the same contact needs to enroll again |
| Potential loop detected | The same steps are being repeatedly triggered in a short time. | Review your flow logic to prevent steps from triggering each other repeatedly. |
Authentication or permission issues
| Remarks error | What it means | Possible solution |
| Authentication failed | The connection credentials are invalid. |
Authentication issues can cause this error. Check whether the connected account is still signed in and authorized to perform this action. |
| Insufficient permissions | The connected account doesn’t have permission to perform the action. |
Missing permissions can cause this issue.
|
| Access token expired | The connection has expired. |
Missing permissions can cause this issue. Your connection may require additional permissions to complete this action. |
| Missing required permissions | Required permission weren’t granted during connection. | Ensure the messaging channel is still connected in Channel settings. |
| IP address blocked | The external platform has blocked requests from this IP address. | Ensure a conversation exists for this contact on the selected channel |
Third-party service issues
| Remarks error | What it means | Possible solution |
| Third-party service unavailable | The external service is temporarily unavailable. |
Temporary service outages can cause this issue. Check the external service status and try again later. |
| Request timed out | The external service took too long to respond. | Slow or unresponsive external services can cause this issue. Try again later. |
| Service is temporarily busy | Requests are being rate-limited by the external platform. |
Rate limits or high request volume can cause this issue. Try again later or reduce how frequently this action is triggered. |
Temporary system issues
| Remarks error | What it means | Possible solution |
| Internal system error | A temporary system issue occurred. |
Internal system issues can cause this issue. Try again later, if the issue persists please contact us for support. |
Plan or usage limits reached
| Remarks error | What it means | Possible solution |
| AI credit limit reached | Your AI credit usage has exceeded the plan limit. |
Plan limits can cause this issue. Check whether your current plan includes enough AI credits for this usage. |
| Enrollment limit reached | The maximum number of enrollments has been reached. |
Enrollment limits can cause this issue. Check whether your plan supports the current enrollment volume. |