Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

WSK API Create endpoint ceases to work after few days

Avatar

Avatar
Give Back
Level 2
vraghav
Level 2

Likes

3 likes

Total Posts

10 posts

Correct Reply

3 solutions
Top badges earned
Give Back
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile

Avatar
Give Back
Level 2
vraghav
Level 2

Likes

3 likes

Total Posts

10 posts

Correct Reply

3 solutions
Top badges earned
Give Back
Boost 3
Boost 1
Affirm 3
Affirm 1
View profile
vraghav
Level 2

18-02-2021

We've created a simple Adobe I/O Runtime action, developed using NodeJS, and successfully deployed our web push integration with Adobe Campaign Standard.
We used the Project Firefly template for the runtime project and used the Campaign STAGE instance for this integration.
The application uses serverless deploy method.

This is fine as expected and we are able to send web push notifications from our ACS instance

 

The issue we're facing is that "wsk api create" commands generate API endpoints that are only available for a few days, after we've noticed that the endpoint of the API returns the 404 exceptions, and again we need to redeploy the application and generate the API endpoint

 

When we've been observing the behaviors, it's basically changing the one alphabet at the endpoint. Rest remains the same. 
How do we generate a static endpoint which basically doesn't change dynamically? The thing is every time the endpoint changes we need to change the respective ACS workflow

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Level 1
stanciu
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
View profile

Avatar
Level 1
stanciu
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
View profile
stanciu
Level 1

23-02-2021

All apis created with `wsk api create` should remain unchanged indefinitely. Could you please share the I/O Runtime namespace, and one of the endpoints that returned 404? I'll do an investigation on what exactly happened.