Overcast for Salesforce uses status code numbers to denomiate the class of success or failure. These are different from the error codes that Overcast Service return in a log message.
| 0 | Waiting to run |
| 100 | Scheduled to run or running |
| 110 | Mapping is scheduled to run or running |
| 200 – 299 | Success |
| 300 – 399 | System error |
| 400 – 499 | Business error. User specified. |
| 500 – 599 | Warning |
| 200 | Run completed successfully |
| 210 | Mapping completed successfully |
| 300 | General faliure. |
| 301 | Terminated manually. |
| 302 | Acknowledge from Overcast Service timed out. |
| 303 |
Invalid run. |
| 304 | Failed to run scenario. |
| 305 | Run time exceeded specified timeout value. |
| 306 | Run already in process. |
| 310 | General mapping failure. |
| 311 | Failed to delete IO records are mapping. |
| 312 | Mapping configuration has an invalid field. |
| 313 | Data conversion error in mapping. |
| 322 | Failed to deploy Overcast Component metadata for Activation. |
| 323 | Failed to get status from Overcast Service for deploying Overcast Component metadata. |
| 324 |
Failed to call Overcast Service to deploy Overcast Component metadata. |
| 325 | Timed out waiting for Overcast Service to deploy Overcast Component metadata. |
| 330 | Failed to schedule Overcast Batch Apex Object Mapper because Batch Apex queue is full. |
| 331 | Failed to update the Run record. |
| 333 | Salesforce record storage limit exceeded in org. |
| 334 | Failure to write logs at end of mapping. |
| 335 | Batch Apex process for Object Mapping failed. |
| 336 | Failure to start the inbound mapping flow. |
| 337 | DML Governor limit hit during the running of the inbound mapping flow. |
| 338 | An error occurred during the running of the inbound mapping flow. |