SecuTix does communicate with external systems.
Those communications are either scheduled (1), either real time (2).
- Each communication to an external system is associated to an object "external interface"
- Each communication to an external system is associated to a schedule associated to this external interface.
- Each communication to an external system is associated to an execution associated to this schedule.
- Every exchanged with an external system should be logged in the execution.
How can I know that something wrong happened with a given execution ?
Answer : the line is red. The status of the execution is KO.
How can I analyse a result ?
- I open the logs of the execution and check for the first lines marked as "error". Most of the a time, an indicator at the begging of the line types the error.
- I read the text of the line. The developer tries his best to provide relevant information. Please read it !
- External → problem during the communication to the external system. Problem in the external system. Action: re-run the action. It does not pass ? Contact the external system provider.
- Configuration → Action: check configuration.
- Mapping → Action: check the mappings.
- Technical → Action: contact support, this an unexpected technical error .
- Cascade → this error comes from another error above. Check above.
I want to communicate with some expert to understand what's wrong with a given execution.
Here are two strategies, one is right, the other one is wrong. The reader must guess which is which.
- I give him the kayako number and nothing more. He logs in, finds the execution, does the analysis, answers to the client.
- I find the execution myself, double clicks on the logs, checks the errors, does an "excel export" (SUPER USEFUL SUPPORT FUNCTION) of the execution and asks the expert for an analysis on the error messages I identified.
(1) Things to know about scheduled (asynchronous) executions
- For scheduled executions, like, for example, "integrate all sales from FNAC every 2 hours", there is an execution created every two hours. You can rerun the executions manually by double clicking on the schedule and ask "run immediately".
- Every scheduled exection is designed to be idempotent. Something failed ? Re-run it. It runs OK ? Problem solved.
- No execution should have a duration greater than 1 hour. If it is the case, this is probably an anomaly.
(2) Things to know about real time (synchronous) executions
- Schedules and executions are "daily". They start at midnight and are closed the next time a new one is started.
- Each time SecuTix calls a realtime interface OR each time an API of SecuTix is closed from the outside, if no daily execution exists, one is created, to contain the logs.
- There is an error in the logs ?
- if SecuTix is the caller, see the log analysis above.
- if SecuTix is the callee, try to understand what call was made provoking the errror. Hint: it should be written in the logs.
Is this interface an API integration ? (support to be pushed to api-support ?)
- If all the executions are "_daily"
- AND if the interface type is "external sales" or "Public webservices SecuTix" or "Exports"
Then it is probably an API based integration and some elements of analysis can be delegated to API support.
