hey. The code implementation takes the URL specified in the configuration files (application-{env}.yml or any other way to provide the value) and concats the "/ui" + the rest of the path to that URL. This could be fixed in the code by removing the slash if specified or to tell users to specify the URL without the slash at the end.

Here is the code creating the final URL:

private URI executionUrl(Execution execution) { return URI.create(kestraUrl.orElse("") + "/ui" + (execution.getTenantId() != null ? "/" + execution.getTenantId(): "") + "/executions/" + execution.getNamespace() + "/" + execution.getFlowId() + "/" + execution.getId() ); }

where kestraUrl is fetched from configuration:

@Value("${kestra.url}") private Optional<String> kestraUrl;

So, did you maybe specify in your application-local.yml or anywhere else the environment variable kestra.url as: "http://localhost:8084/"?

@loicmathieu what do you think?

Hey @anna-geller,

Is there an internal decision to handle this case? If so, I’d be happy to take care of it.

Also, @wrussell1999 could you confirm whether the / was added to the configuration somewhere?

Hi @benjoEK1337, we would love to see your contribution. There are no internal discussions about this — in the end, we can't guarantee that the user adds a trailing slash in their configuration file so the code needs to:

1. check if the the KESTRA_URL is set
2. if yes, then we need to check if it ends with / and we need to append a trailing slash to the API response if the slash is missing at the end
3. if no, no url should be returned in the payload

WDYT? does it sound like a good plan to you? 🚀

I think that the expected behavior for the user is not to add the trailing slash. The current implementation doesn't expect the trailing slash, so if the user adds a trailing slash, the returned URL contains two trailing slashes. So, my suggestion for implementation is to check if the user added a trailing slash, and then remove it in the code.

Regarding the case when KESTRA_URL is not set, the current logic is handling it this way:

1. check if the KESTRA_URL is set
2. If yes, append to the KESTRA_URL these: "/ui" plus the rest of the path containing tenant ID (if it exists), namespace, flow ID, and ID. For example - "url": "http://localhost:8084//ui/executions/company.team/hello_world/6gTABm82mx5li7tHkgqyNU"
3. If no, return the URL in the format "url": "/ui/executions/company.team/hello_world/6gTABm82mx5li7tHkgqyNU"

So if no KESTRA URL is set, it doesn't include the KESTRA_URL in the returned URL.

So should we change to not return the URL when the KESTRA_URL is not set, as you suggested, or keep this part of the logic as it is?

The current behavior seems fine. Looking forward to your PR! Thanks for looking into this

Hey @anna-geller, I created the PR. Could you please assign me to this task and add a reviewer to the PR? Thanks 🚀