awslabs / awslabs/aws-appflow-custom-connector-java
About error handling when using a custom connector as a destination
- Dominant language
- Java
- Stars
- 20
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
We are currently implementing a custom connector.
Please tell me about error handling when using a custom connector as a destination.
In the "Configure flow" step of AppFlow, following configuration items related to error handling would appear on the screen (Use S3 as the source) .

(Question)
There are two options "Stop the current flow run" and "Ignore and continue the flow run", are these options handled by the AppFlow infrastructure and not something we need to be aware of in the custom connector?
Also, if it is handled on the AppFlow infrastructure side, could you please tell me exactly how each option works?
(Background)
①
It appears that `com.amazonaws.appflow.custom.connector.connector.model.writeWriteDataRequest` does not hold that configuration item, and I believe there is no way for the custom connector implementation to know which one the user has chosen. Therefore, I did not think it was a setting item to be handled on the custom connector side.
②
I tried both options and could not understand the difference in behavior. Both seemed to have the "Ignore and continue the flow run" behavior (In both cases, when returning a WriteDataResponse with isSucecss false and when throwing an Exception, the process seemed to stop).
Contributor guide
Research direction
Start by reviewing the custom connector model class com.amazonaws.appflow.custom.connector.connector.model.writeWriteDataRequest and the reported WriteDataResponse and exception behavior. Compare those details with the two AppFlow error-handling options shown in the issue, then document the distinction and how each option should behave for a destination connector.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100