the error seems to indicate that the step that initiated the write has as input a DynamicFrame with some data issue. It could be a special characters that splits one record in two lines, but it is not really possible to say with the limited info.
You should try to look at the logs of the job.
In Glue Studio open the jobs then select the tab Runs or in the left pane select Monitoring then follow the instruction in this documentation page.
You can also try to enable run insight to get a different formatting for the logs, that should be easier to read.
hope this helps, if you are not able to find the issue, please update the question with more info from the logs, and about your job.
Glue Job Fails | s3 to db/mysql | An error occurred while calling o87.getCatalogSink. None.getasked 10 days ago
An error occurred while calling o95.pyWriteDynamicFrame.asked 8 months ago
An error occurred while calling o187.pyWriteDynamicFrame. Unable to execute HTTP request:asked 5 months ago
AWS Glue Studio Job Failed An error occurred while calling o106.pyWriteDynamicFrame. Data truncation: Data too long for column [insertcolumnname] at row 1asked a month ago
An error occurred while calling o280.pyWriteDynamicFrameasked 4 years ago
An error occurred while calling o110.pyWriteDynamicFrame. nullasked 2 months ago
An error occurred while calling o128.pyWriteDynamicFrame. Record is incomplete.asked 6 months ago
AWS Glue gives error: "An error occurred while calling o285.save. File already exists:"asked 9 months ago
Glue Job Error (An error occurred while calling o100.pyWriteDynamicFrame. Illegal empty schema)Accepted Answerasked 6 months ago
An error occurred while calling o352.pyWriteDynamicFrame. Job 1 cancelled because SparkContext was shut down caused by threshold for consecutive task creation reachedasked 3 months ago