Do you have an error and are feeling lost in the vast world of APIs and Cloud Elements?
Hopefully this will provide some much needed context and direction.
Whenever you are troubleshooting you want to minimize the variables to isolate the issue.
Think of Cloud Elements as a layer on top of any original endpoints APIs. Likewise,
any additional features you use on Cloud Elements such as formulas, transformations or bulk,
add additional layers of functionality. This means more variables.
The goal of troubleshooting Cloud Elements is to tear off layer by layer of functionality
until you find where the issue is.
Lets say you have a formula, and it is failing. Lets go through the steps in a hypothetical situation:
1. Look at the formula execution logs to determine what step is failing.
You find it was failing on a Element Request Step. Now you know that its an API call that's failing. Great, lets remove the "layer" of formulas. From the execution log, you can see that the request is:
The request is using a transformation, that's another layer.
2. Get the payload that was being sent in the formula from the execution logs and test the API outside of the formula
POST /MyCustomObject and see that its failing with a 500 Internal Server Error. Perfect.
3. Make sure the instance is working.
You call another API on that endpoint without using your transformation and it works fine.
Lets say your transformation is mapped to contacts. Try transforming the data yourself and create a contact with the same data.
That works. So the transformation is the problem.
GET /MyCustomObject to see what the data looks like when you retrieve it.
You find it looks weird. firstName is mapped to a date field. The problem is on the transformation.
This same strategy should be used with any "layer" on Cloud Elements, like events, bulk, elements builder. Remember that each feature you use adds "layer" on top of the original API, whatever it may be. When debugging, remove as many layers as possible to get to the root of the issue.