Custom Plugin FAQ

This article summarizes some of the questions you may encounter when developing plugins. If you are still bothered by some questions after reading the article, contact our Support Team.

How to debug and develop plugin codes locally?

The plugin code itself is a method body. Therefore, it needs to be wrapped in code packaging at the outer layer before calling and debugging.

After local debugging, you can copy the plugin code to Jodoo, and click Plugin Debug to debug in the actual operating environment.

What are the applicable scenarios for plugins?

By defining the format of input and output, you can customize the plugin based on actual business needs.

Plugins are not suitable for handling long-term operations. The current timeout of the plugin itself is 60s. And the timeouts vary in different scenarios, such as 20s for front-end events.

Does the current plugin support the base64 module?

The Base64 module is included in Python. You can import the module into your Python code to use it.

Why can't the returned image address be accessed?

Jodoo link currently has an expiration date. If it is processed after the expiration date, an error will be displayed.

Why are the times obtained in local and plugin different for the same code?

The plugin server is in the UTC time zone, and the local code depends on the time zone of the developer's local server. Due to the time zone difference where the server is located, the actual time obtained from running the same code locally and in the plugin may be different.

Why can't the returned image be directly written back to the image field?

Currently, in the scenario of front-end event triggering, the plugin does not support directly writing images to image fields. Instead, it can only return the image URL to a text field.

To avoid risks, there are no plans to develop the feature of writing back the returned image/attachment to the corresponding fields in the short term.

Why does the plugin report an error when the optional common parameters of the plugin are not configured or cleared after configuration?

When common parameters are not configured, their initial value is null instead of being empty. Therefore, common parameters should be set to null when they are not filled.

Is the IP of the plugin fixed?

The server IP address is fixed: 13.251.218.18.

Can't the plugin trigger repeatedly on schedule?

Currently, the custom plugin supports scheduled triggering, but the minimum granularity is once a day.

You are not allowed to achieve real-time or finer-grained scheduled automatic triggering.

However, through the button feature to be launched in subsequent plans, users can repeat triggers without opening the data details page.

The images in URL format are not supported in some APIs, how to handle?

You can first download the image, then send it after parsing the image URL into a string in base64 format.

More frequently asked questions, continuously updated...