Error codes
All returned errors have the following form:
{
error_code: <int>,
error_message: <string>,
more_info: <string>
}Code description
500
{
error_code: 500,
error_message: 'Internal error',
more_info: 'https://mixapp.github.io/main/errors/#500'
}Internal error, error data logged additionally.
600
{
error_code: 600,
error_message: 'Workplace not found',
more_info: 'https://mixapp.github.io/main/errors/#600'
}Error occurs when a non-existent workplace is addressed.
601
Error occurs when an invalid scheme is transmitted or when an error has occurred in the type of transmitted data while saving or updating.
602
Error occurs if this workplace already exists.
603
Error occurs if workplace name in the query has a wrong format or is empty.
604
Error occurs if an invalid scheme is transmitted while creating the storage or if an error has occurred in the type of transmitted data while saving or updating.
605
Invalid ACL transmitted in the query.
606
Maximum number of storages reached.
607
A storage with this name already exists.
608
Storage name cannot be less than 3 symbols.
609
Error occurs when a non-existent storage is requested.
610
Invalid storage identifier transmitted.
611
Invalid index transmitted.
612
Invalid format transmitted for working with storage files.
613
Invalid process data transmitted or an error has occurred in the type of data transmitted.
614
Process name cannot be less than 3 symbols.
615
Variable name empty or invalid.
616
Unknown variable type transmitted.
617
Invalid ACL transmitted.
618
Non-existent or remote process requested.
619
This error occurs when updating a running process is attempted.
620
Invalid process identifier transmitted.
621
Invalid connector format transmitted or an error has occurred in connector type.
622
Unknown connector type transmitted.
623
Error occurs at connector validation and indicates that an obligatory section in connector parameters has been omitted.
624
Error occurs when trying to create a “start” or “stop” type connector.
625
Error occurs if the user handler for connector parameters returns an error at validation. Error text is set by the user in the handler.
626
Invalid connector identifier transmitted.
627
Error occurs when a non-existent connector is addressed.
628
Error occurs at connector update if a type is transmitted that does not correspond to the initial type.
629
Error occurs when the connector tries to connect to itself.
630
Error occurs at attempt to create a connector with a “stop” type outbound connection.
631
Error occurs if more than one child connector attempts to connect to the timer.
632
Error occurs at connection attempt when a “start” connector acts as a child connector.
633
Error occurs if more than one parent connector attempts to connect to the timer.
634
Error occurs if a connection between the connectors already exists.
635
Error occurs if no connection between the connectors has been established.
636
Connection name can only be established for steps of the following type: “case”, “task”.
637
Error occurs when creating connection name, if the branch for this name is not specified in the parameters of the “results” section.
638
Error occurs when validating the “results” section for a “case” type step, if the child connector identifier is already contained in the array for this section.
639
Error occurs if an invalid scheme is transmitted for the variable or if an error has occurred in the type of data transmitted.
640
Error occurs if an existing variable is created.
641
Error occurs if an invalid string type is transmitted in the “value” section.
642
Error occurs if an invalid date type is transmitted in the “value” section.
643
Error occurs if no values for obligatory variables were transmitted in the request when creating the process.
644
Error occurs if the transmitted variable has a different type at the time of process creation.
645
Error occurs if the handled connector has no connection to the parent connector.
646
Error occurs if the connector to be handled has no connection to the executing connector.
647
The error occurs if an invalid identifier of the inherited connector is transmitted.
648
The error occurs if the inherited connector is not found.
649
The error occurs if an invalid or empty e-mail is transmitted.
650
User name must contain at least 5 characters
651
The error occurs if an invalid npm module value is transmitted.
652
The error occurs if this user name already exists in the system
653
The error occurs if invalid user data has been transmitted
654
The error occurs if the rights for the action are insufficient.
655
The error occurs if authorization is required
656
Password must contain at least 8 characters
657
Index name is empty
658
Owner is empty
659
Title is empty
660
Order schema is invalid
661
Invalid planId
662
Invalid userId
663
Plan not found
664
Insufficient funds
665
User not found
666
Key schema isn't valid
667
Context not found
668
Webhook not found
669
Errors while executing the connector
670
Connector schema isn't valid
671
Connector name is empty
672
Connector must have exutable code
673
Connector contained invalid param
674
Not implementate yet
675
Can not remove a system connector
Last updated
Was this helpful?