Flow Service error messages

Last update: April 2, 2025

CREATED FOR:

  • Developer

Flow Service is used to collect and centralize customer data from various disparate sources within Experience Platform. The service provides a user interface and RESTful API that lets you set-up source connections to various data providers with ease. These source connections enable you to authenticate your third-party systems, set times for ingestion runs, and manage data ingestion throughput.

This document provides a catalog of error messages, descriptions, and suggested resolutions regarding Flow Service.

Internal validation errors in Flow Service

The following table outlines errors regarding internal validation in Flow Service.

Error code
Title
Detailed message
1100-400
Invalid request
The request could not be processed. Error from flow provider: Not entitled to this operation.
1101-404
Resource not found
The requested resource is not found. Error from flow provider: Resource with given id does not exist.
1102-500
Internal Error
An internal error has occurred. Please try again. If the problem persists, please contact customer support.
1103-503
Service Unavailable
The service is temporarily unavailable. Please try again. If the problem persists, please contact customer support.
1104-504
Gateway Timeout
A gateway timeout has occurred. Please try again. If the problem persists, please contact customer support.
1400-500
Internal Error
An internal error has occurred. Please try again. If the problem persists, please contact customer support.
1401-400
Invalid request
The limit and count parameters cannot be given together in the same request. Please provide either only the limit or the count parameter and try again.
1402-400
Invalid request
The action ‘finalize’ is supported for provider requests only.
1403-400
Header is missing
The header ‘If-Match’ is missing in the request. Please provide the header and try again.
1404-412
Version not matching
The supplied version ‘v1’ does not match the current version on entity ‘cc01fc2c-0000-0200’. Please ensure that the supplied version matches the current version on entity and try again.
1405-400
Invalid request
The request body cannot be null or empty. Please provide a request body and try again.
1406-400
Invalid request
The sub operation ‘progress’ cannot be applied with other sub operations. Please update the sub operations list and try again.
1407-400
Invalid request
The status failed cannot be used with the progress subOp. Please remove the progress subOp or use the status=‘inProgress’ and try again.
1408-400
Invalid request
The percent-completed should be 100 for the completed or failed states. Please update the percent-completed and try again.
1409-400
Invalid request
The operation ‘finalize’ cannot be applied on the current state enabled-finalizing. Please update the operation and try again.
1410-400
Invalid request
State is not allowed in the create flow request.
1411-400
Invalid request
Unable to retrieve entityId. Invalid request received with path ‘baseConnections/123’.
1412-400
Invalid request
Invalid Mapping Version in request. Please provide correct mapping version.
1413-400
Invalid request
The spec ID provided is invalid. Please provide a valid spec ID and try again.
1414-400
Invalid request
The connection spec of a connection cannot be updated.
1415-400
Invalid request
The auth spec ‘authConnection’ could not be found for the connection spec ID ba6e206f-f233-ab16.
1416-400
Invalid request
Delete or Update can only be applied on connection with enabled, disabled or initializing state.
1417-400
Invalid request
Delete or Update on Connections in initializing state are not allowed with UserToken.
1418-400
Invalid request
The base connection with the ID 35dcaad3-122a-4278 cannot be deleted because the base connection is being used in one or more flows. Please ensure that corresponding flows are deleted before deleting a base connection.
1419-400
Invalid request
Error while validating mapping with id 45d90285d2d249acb87a72a2f12f7401, version 0. This could be because of inadequate permissions on mapped fields. Please check your mapping or contact your admin.
1420-400
Invalid request
The current state disabling cannot be updated.
1421-400
Invalid request
The current state updating cannot be transitioned.
1422-400
Invalid request
The action disable cannot be applied on the current state {state}. Please update the action and try again.
1423-400
Invalid request
An unhandled field baseSpec was provided in ConnectionSpecFiltering. Please update the field {field} and try again.
1424-400
Invalid request
OrderBy is not supported with cross sandbox query.
1425-400
Invalid request
Error while matching schema in target dataset 64ef1a3c0ef with schema in mapping 91ac5a2c0eb. Schema with same id and version must be used in both mapping and target dataset.
1426-400
Invalid request
The user token is unauthorized to create/update the connection spec. Please ensure that the user token is authorized and try again.
1427-400
Invalid request
The user token is unauthorized to create/update flow runs. Please ensure that the user token is authorized and try again.
1428-400
Invalid request
Predecessor flow run not found with id aa6a206f-f233-4c2d.
1429-400
Invalid request
Predecessor flow not found with id aa6a206f-f233-4c2d.
1430-400
Invalid request
Flow not found with id aa6a206f-f233-4c2d.
1431-400
Invalid request
Empty array ‘fields’ is not allowed in policy.
1432-400
Invalid request
Sort order specified is not correct, prepend + for ascending order and - for descending order in the fieldName.
1433-400
Invalid request
Incorrect field= #id passed in orderBy, example are +name, -name, name.
1434-400
Invalid request
Unsupported operation ‘move’ received. Please use one of the supported operation types and try again.
1435-400
Invalid request
Unsupported sub action ‘reverse’ received. Please use one of the supported sub action types and try again.
1436-400
Invalid request
Unsupported sub operation PROGRESS received for operation enable.
1437-400
Invalid request
Unsupported status value ‘started’ received. Please update the status value and try again.
1438-400
Invalid request
Unsupported aggregate operation ‘average’ received.
1439-400
Resource not found
The requested flows resource 3f4ae131-b384-4e73 is not found. Verify the resource ID before trying again.
1440-400
Invalid request
Operator ‘~’ not implemented.
1441-400
Invalid request
Aggregate function ‘average’ not implemented.
1442-400
Invalid request
Aggregation not allowed on field id.
1443-400
Invalid request
Operator ‘<=’ is not allowed for multiple values.
1444-400
Invalid request
Flow 3f4ae131-b384-4e73 is not in expected state pending.
1445-400
Invalid request
PATCH Connection Feature not enabled.
1446-400
Invalid request
The flow ID cannot be null or empty. Please update the flow ID and try again.
1447-400
Invalid request
Found active flows containing id aa6a206f-f233-4c2d.
1448-400
Invalid request
Operator >= not supported for field id.
1449-400
Invalid request
Invalid field connections in filter params.
1450-400
Invalid request
Invalid operator !> in filter params.
1451-400
Invalid request
Invalid params testParam provided in query params.
1452-400
Invalid request
Invalid value 1676643256,1676643210 for field createdAt.
1453-400
Invalid request
Invalid query value createdAt== provided in query param.
1454-400
Invalid request
Unhandled Filter Value Type provided.
1455-400
Invalid request
An error has occurred while validating patch instructions: Missing field “keyWhichDoesNotExist”.
1456-400
Invalid request
State delete-finalizing is not a valid value. Allowed values are [enabled, disabled, initializing].
1457-400
Invalid request
Operation update cannot be applied in state delete-finalizing.
1458-400
Invalid request
Operation delete cannot be applied in state delete-finalizing.